Multiple child windows in dual display communication devices

ABSTRACT

The present disclosure is directed to methodologies and devices for handling maximizing and minimizing of hierarchically related windows.

CROSS REFERENCE TO RELATED APPLICATION

The present application is a continuation of and claims priority to U.S.patent application Ser. No. 13/247,823, filed Sep. 28, 2011, of the sametitle, which claims the benefits of and priority, under 35 U.S.C.§119(e), to U.S. Provisional Application Ser. No. 61/389,000, filed Oct.1, 2010, entitled “DUAL DISPLAY WINDOWING SYSTEM;” 61/389,117, filedOct. 1, 2010, entitled “MULTI-OPERATING SYSTEM PORTABLE DOCKETINGDEVICE;” 61/389,087, filed Oct. 1, 2010, entitled “TABLET COMPUTING USERINTERFACE;”61/458,150, filed Nov. 17, 2010, entitled “Dual Screen EmailClient;” 61/539,884, filed Sep. 27, 2011, entitled “MOBILE DEVICE.” Eachof the aforementioned documents is incorporated herein by this referencein their entirety for all that they teach and for all purposes.

BACKGROUND

A substantial number of handheld computing devices, such as cellularphones, tablets, and E-Readers, make use of a touch screen display notonly to deliver display information to the user but also to receiveinputs from user interface commands. While touch screen displays mayincrease the configurability of the handheld device and provide a widevariety of user interface options, this flexibility typically comes at aprice. The dual use of the touch screen to provide content and receiveuser commands, while flexible for the user, may obfuscate the displayand cause visual clutter, thereby leading to user frustration and lossof productivity.

The small form factor of handheld computing devices requires a carefulbalancing between the displayed graphics and the area provided forreceiving inputs. On the one hand, the small display constrains thedisplay space, which may increase the difficulty of interpreting actionsor results. On the other hand, a virtual keypad or other user interfacescheme is superimposed on or positioned adjacent to an executingapplication, requiring the application to be squeezed into an evensmaller portion of the display.

This balancing act is particularly difficult for single display touchscreen devices. Single display touch screen devices are crippled bytheir limited screen space. When users are entering information into thedevice, through the single display, the ability to interpret informationin the display can be severely hampered, particularly when a complexinteraction between display and interface is required.

SUMMARY

There is a need for a dual multi-display handheld computing device thatprovides for enhanced power and/or versatility compared to conventionalsingle display handheld computing devices. These and other needs areaddressed by the various aspects, embodiments, and/or configurations ofthe present disclosure. Also, while the disclosure is presented in termsof exemplary embodiments, it should be appreciated that individualaspects of the disclosure can be separately claimed.

In one embodiment, a method is provided that includes the steps of:

-   -   receiving, by processor executable middleware in a multi-display        communication device, a command to at least one of minimize and        maximize a set of related windows from a common multi-screen        application, the set of related windows comprising a higher        level window and a lower level window at least one of displayed        and to be displayed by different touch sensitive displays;

applying, by the processor executable middleware, the following rules:

-   -   (B1) when the set of related windows is to be minimized,        selecting a touch sensitive display for displaying the higher        level window and ceasing to display the lower level window on        the other touch sensitive display; and        -   (B2) when the set of related windows is to be maximized,            selecting a predetermined touch sensitive display for            displaying one of the higher and lower level window and            causing the other of the higher and lower level window to be            displayed on the other touch sensitive display.

In one embodiment, a communication device is provided that includes:

at least first and second touch sensitive displays to display windows;

a processor; and

a computer readable memory, the computer readable memory comprisingprocessor executable middleware operable to:

receive a command to at least one of minimize and maximize a set ofrelated windows from a common multi-screen application, the set ofrelated windows comprising a higher level window and a lower levelwindow at least one of displayed and to be displayed by different touchsensitive displays;

apply the following rules:

-   -   (i) when the set of related windows is to be minimized,        selecting a touch sensitive display for displaying the higher        level window and ceasing to display the lower level window on        the other touch sensitive display; and    -   (ii) when the set of related windows is to be maximized,        selecting a predetermined touch sensitive display for displaying        one of the higher and lower level window and causing the other        of the higher and lower level window to be displayed on the        other touch sensitive display.

In one configuration, the set of related windows is maximized, thecommand is a drag or a flick, neither the higher nor lower level windowis displayed in the predetermined touch sensitive display when thegesture is received, and the lower level window appears to move from theother touch sensitive display to the predetermined touch sensitivedisplay, thereby revealing the higher level window in the other touchsensitive display.

In one configuration, the set of related windows is maximized, thecommand is a drag or a flick, the lower level window is in thepredetermined touch sensitive display when the gesture is received, andthe higher level window appears to move from the predetermined touchsensitive display to the other touch sensitive display, whereby thelower level window is displayed by the predetermined touch sensitivedisplay and the higher level window is displayed by the other touchsensitive display.

In one configuration, the set of related windows is maximized, themulti-display communication device is in the portrait display mode, andthe predetermined touch sensitive display is the right-most touchsensitive display.

In one configuration, the set of related windows is minimized, thecommand is a drag or a flick, the higher and lower level window areconcurrently displayed in the selected and other touch sensitivedisplays when the gesture is received, the lower level display isdisplayed in the selected touch sensitive display when the gesture isreceived, and the higher level window appears to move from the othertouch sensitive display to the selected touch sensitive display, therebycovering the lower level window in the other touch sensitive display.

In one configuration, the set of related windows is minimized, thecommand is a drag or a flick, the higher and lower level window areconcurrently displayed in the selected and other touch sensitivedisplays when the gesture is received, the higher level display isdisplayed in the selected touch sensitive display when the gesture isreceived, and the lower level window appears to move from the othertouch sensitive display to the selected touch sensitive display, therebydisappearing under the higher level window in the other touch sensitivedisplay.

The present disclosure can provide effective and convenient rules tohandle displayed images, particularly hierarchically related windows.

These and other advantages will be apparent from the disclosure.

The phrases “at least one”, “one or more”, and “and/or” are open-endedexpressions that are both conjunctive and disjunctive in operation. Forexample, each of the expressions “at least one of A, B and C”, “at leastone of A, B, or C”, “one or more of A, B, and C”, “one or more of A, B,or C” and “A, B, and/or C” means A alone, B alone, C alone, A and Btogether, A and C together, B and C together, or A, B and C together.

The term “a” or “an” entity refers to one or more of that entity. Assuch, the terms “a” (or “an”), “one or more” and “at least one” can beused interchangeably herein. It is also to be noted that the terms“comprising”, “including”, and “having” can be used interchangeably.

The term “automatic” and variations thereof, as used herein, refers toany process or operation done without material human input when theprocess or operation is performed. However, a process or operation canbe automatic, even though performance of the process or operation usesmaterial or immaterial human input, if the input is received beforeperformance of the process or operation. Human input is deemed to bematerial if such input influences how the process or operation will beperformed. Human input that consents to the performance of the processor operation is not deemed to be “material”.

The term “computer-readable medium” as used herein refers to anytangible storage and/or transmission medium that participate inproviding instructions to a processor for execution. Such a medium maytake many forms, including but not limited to, non-volatile media,volatile media, and transmission media. Non-volatile media includes, forexample, NVRAM, or magnetic or optical disks. Volatile media includesdynamic memory, such as main memory. Common forms of computer-readablemedia include, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, or any other magnetic medium, magneto-optical medium, aCD-ROM, any other optical medium, punch cards, paper tape, any otherphysical medium with patterns of holes, a RAM, a PROM, and EPROM, aFLASH-EPROM, a solid state medium like a memory card, any other memorychip or cartridge, a carrier wave as described hereinafter, or any othermedium from which a computer can read. A digital file attachment toe-mail or other self-contained information archive or set of archives isconsidered a distribution medium equivalent to a tangible storagemedium. When the computer-readable media is configured as a database, itis to be understood that the database may be any type of database, suchas relational, hierarchical, object-oriented, and/or the like.Accordingly, the disclosure is considered to include a tangible storagemedium or distribution medium and prior art-recognized equivalents andsuccessor media, in which the software implementations of the presentdisclosure are stored.

The term “desktop” refers to a metaphor used to portray systems. Adesktop is generally considered a “surface” that typically includespictures, called icons, widgets, folders, etc. that can activate showapplications, windows, cabinets, files, folders, documents, and othergraphical items. The icons are generally selectable to initiate a taskthrough user interface interaction to allow a user to executeapplications or conduct other operations.

The term “screen,” “touch screen,” or “touchscreen” refers to a physicalstructure that includes one or more hardware components that provide thedevice with the ability to render a user interface and/or receive userinput. A screen can encompass any combination of gesture capture region,a touch sensitive display, and/or a configurable area. The device canhave one or more physical screens embedded in the hardware. However ascreen may also include an external peripheral device that may beattached and detached from the device. In embodiments, multiple externaldevices may be attached to the device. Thus, in embodiments, the screencan enable the user to interact with the device by touching areas on thescreen and provides information to a user through a display. The touchscreen may sense user contact in a number of different ways, such as bya change in an electrical parameter (e.g., resistance or capacitance),acoustic wave variations, infrared radiation proximity detection, lightvariation detection, and the like. In a resistive touch screen, forexample, normally separated conductive and resistive metallic layers inthe screen pass an electrical current. When a user touches the screen,the two layers make contact in the contacted location, whereby a changein electrical field is noted and the coordinates of the contactedlocation calculated. In a capacitive touch screen, a capacitive layerstores electrical charge, which is discharged to the user upon contactwith the touch screen, causing a decrease in the charge of thecapacitive layer. The decrease is measured, and the contacted locationcoordinates determined. In a surface acoustic wave touch screen, anacoustic wave is transmitted through the screen, and the acoustic waveis disturbed by user contact. A receiving transducer detects the usercontact instance and determines the contacted location coordinates.

The term “display” refers to a portion of one or more screens used todisplay the output of a computer to a user. A display may be asingle-screen display or a multi-screen display, referred to as acomposite display. A composite display can encompass the touch sensitivedisplay of one or more screens. A single physical screen can includemultiple displays that are managed as separate logical displays. Thus,different content can be displayed on the separate displays althoughpart of the same physical screen.

The term “displayed image” refers to an image produced on the display. Atypical displayed image is a window or desktop. The displayed image mayoccupy all or a portion of the display.

The term “display orientation” refers to the way in which a rectangulardisplay is oriented by a user for viewing. The two most common types ofdisplay orientation are portrait and landscape. In landscape mode, thedisplay is oriented such that the width of the display is greater thanthe height of the display (such as a 4:3 ratio, which is 4 units wideand 3 units tall, or a 16:9 ratio, which is 16 units wide and 9 unitstall). Stated differently, the longer dimension of the display isoriented substantially horizontal in landscape mode while the shorterdimension of the display is oriented substantially vertical. In theportrait mode, by contrast, the display is oriented such that the widthof the display is less than the height of the display. Stateddifferently, the shorter dimension of the display is orientedsubstantially horizontal in the portrait mode while the longer dimensionof the display is oriented substantially vertical.

The term “composited display” refers to a logical structure that definesa display that can encompass one or more screens. A multi-screen displaycan be associated with a composite display that encompasses all thescreens. The composite display can have different displaycharacteristics based on the various orientations of the device.

The term “gesture” refers to a user action that expresses an intendedidea, action, meaning, result, and/or outcome. The user action caninclude manipulating a device (e.g., opening or closing a device,changing a device orientation, moving a trackball or wheel, etc.),movement of a body part in relation to the device, movement of animplement or tool in relation to the device, audio inputs, etc. Agesture may be made on a device (such as on the screen) or with thedevice to interact with the device.

The term “module” as used herein refers to any known or later developedhardware, software, firmware, artificial intelligence, fuzzy logic, orcombination of hardware and software that is capable of performing thefunctionality associated with that element.

The term “gesture capture” refers to a sense or otherwise a detection ofan instance and/or type of user gesture. The gesture capture can occurin one or more areas of the screen, A gesture region can be on thedisplay, where it may be referred to as a touch sensitive display or offthe display where it may be referred to as a gesture capture area.

A “multi-screen application” refers to an application that is capable ofmultiple modes. The multi-screen application mode can include, but isnot limited to, a single screen mode (where the application is displayedon a single screen) or a composite display mode (where the applicationis displayed on two or more screens). A multi-screen application canhave different layouts optimized for the mode. Thus, the multi-screenapplication can have different layouts for a single screen or for acomposite display that can encompass two or more screens. The differentlayouts may have different screen/display dimensions and/orconfigurations on which the user interfaces of the multi-screenapplications can be rendered. The different layouts allow theapplication to optimize the application's user interface for the type ofdisplay, e.g., single screen or multiple screens. In single screen mode,the multi-screen application may present one window pane of information.In a composite display mode, the multi-screen application may presentmultiple window panes of information or may provide a larger and aricher presentation because there is more space for the displaycontents. The multi-screen applications may be designed to adaptdynamically to changes in the device and the mode depending on whichdisplay (single or composite) the system assigns to the multi-screenapplication. In alternative embodiments, the user can use a gesture torequest the application transition to a different mode, and, if adisplay is available for the requested mode, the device can allow theapplication to move to that display and transition modes.

A “single-screen application” refers to an application that is capableof single screen mode. Thus, the single-screen application can produceonly one window and may not be capable of different modes or differentdisplay dimensions. A single-screen application is incapable of theseveral modes discussed with the multi-screen application.

The term “window” refers to a, typically rectangular, displayed image onat least part of a display that contains or provides content differentfrom the rest of the screen. The window may obscure the desktop.

The terms “determine”, “calculate” and “compute,” and variationsthereof, as used herein, are used interchangeably and include any typeof methodology, process, mathematical operation or technique.

It shall be understood that the term “means” as used herein shall begiven its broadest possible interpretation in accordance with 35 U.S.C.,Section 112, Paragraph 6. Accordingly, a claim incorporating the term“means” shall cover all structures, materials, or acts set forth herein,and all of the equivalents thereof. Further, the structures, materialsor acts and the equivalents thereof shall include all those described inthe summary of the invention, brief description of the drawings,detailed description, abstract, and claims themselves.

The preceding is a simplified summary of the disclosure to provide anunderstanding of some aspects of the disclosure. This summary is neitheran extensive nor exhaustive overview of the disclosure and its variousaspects, embodiments, and/or configurations. It is intended neither toidentify key or critical elements of the disclosure nor to delineate thescope of the disclosure but to present selected concepts of thedisclosure in a simplified form as an introduction to the more detaileddescription presented below. As will be appreciated, other aspects,embodiments, and/or configurations of the disclosure are possibleutilizing, alone or in combination, one or more of the features setforth above or described in detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A includes a first view of an embodiment of a multi-screen userdevice;

FIG. 1B includes a second view of an embodiment of a multi-screen userdevice;

FIG. 1C includes a third view of an embodiment of a multi-screen userdevice;

FIG. 1D includes a fourth view of an embodiment of a multi-screen userdevice;

FIG. 1E includes a fifth view of an embodiment of a multi-screen userdevice;

FIG. 1F includes a sixth view of an embodiment of a multi-screen userdevice;

FIG. 1G includes a seventh view of an embodiment of a multi-screen userdevice;

FIG. 1H includes a eighth view of an embodiment of a multi-screen userdevice;

FIG. 1I includes a ninth view of an embodiment of a multi-screen userdevice;

FIG. 1J includes a tenth view of an embodiment of a multi-screen userdevice;

FIG. 2 is a block diagram of an embodiment of the hardware of thedevice;

FIG. 3A is a block diagram of an embodiment of the state model for thedevice based on the device's orientation and/or configuration;

FIG. 3B is a table of an embodiment of the state model for the devicebased on the device's orientation and/or configuration;

FIG. 4A is a first representation of an embodiment of user gesturereceived at a device;

FIG. 4B is a second representation of an embodiment of user gesturereceived at a device;

FIG. 4C is a third representation of an embodiment of user gesturereceived at a device;

FIG. 4D is a fourth representation of an embodiment of user gesturereceived at a device;

FIG. 4E is a fifth representation of an embodiment of user gesturereceived at a device;

FIG. 4F is a sixth representation of an embodiment of user gesturereceived at a device;

FIG. 4G is a seventh representation of an embodiment of user gesturereceived at a device;

FIG. 4H is a eighth representation of an embodiment of user gesturereceived at a device;

FIG. 5A is a block diagram of an embodiment of the device softwareand/or firmware;

FIG. 5B is a second block diagram of an embodiment of the devicesoftware and/or firmware;

FIG. 6A is a first representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6B is a second representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6C is a third representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6D is a fourth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6E is a fifth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6F is a sixth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6G is a seventh representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6H is a eighth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6I is a ninth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 6J is a tenth representation of an embodiment of a deviceconfiguration generated in response to the device state;

FIG. 7 is a flow chart according to an embodiment;

FIG. 8 is a root view of a plurality of windows controlled by a commonmulti-screen application;

FIG. 9A is representation of a logical window stack;

FIG. 9B is another representation of an embodiment of a logical windowstack;

FIG. 9C is another representation of an embodiment of a logical windowstack;

FIG. 9D is another representation of an embodiment of a logical windowstack;

FIG. 9E is another representation of an embodiment of a logical windowstack;

FIG. 10 is block diagram of an embodiment of a logical data structurefor a window stack;

FIG. 11 is a flow chart of an embodiment of a method for creating awindow stack;

FIG. 12 depicts a window stacking configuration according to anembodiment;

FIGS. 13A-C are a series of portrait display orientation screen shotsaccording to an embodiment;

FIGS. 14A-C are a series of portrait display orientation screen shotsaccording to an embodiment;

FIGS. 15A-C are a series of portrait display orientation screen shotsaccording to an embodiment;

FIGS. 16A-C are a series of portrait display orientation screen shotsaccording to an embodiment;

FIGS. 17A-C are a series of portrait display orientation screen shotsaccording to an embodiment;

FIGS. 18A-C are a series of portrait display orientation screen shotsaccording to an embodiment;

FIGS. 19A-C are a series of portrait display orientation screen shotsaccording to an embodiment;

FIGS. 20A-C are a series of landscape display orientation screen shotsaccording to an embodiment;

FIGS. 21A-C are a series of landscape display orientation screen shotsaccording to an embodiment;

FIGS. 22A-C are a series of landscape display orientation screen shotsaccording to an embodiment;

FIGS. 23A-C are a series of landscape display orientation screen shotsaccording to an embodiment;

FIGS. 24A-C are a series of portrait display orientation screen shotsaccording to an embodiment;

FIGS. 25A-C are a series of portrait display orientation screen shotsaccording to an embodiment;

FIGS. 26A-C are a series of portrait display orientation screen shotsaccording to an embodiment; and

FIG. 27 is a flow chart according to an embodiment.

In the appended figures, similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a letter thatdistinguishes among the similar components. If only the first referencelabel is used in the specification, the description is applicable to anyone of the similar components having the same first reference labelirrespective of the second reference label.

DETAILED DESCRIPTION

Presented herein are embodiments of a device. The device can be acommunications device, such as a cellular telephone, or other smartdevice. The device can include two screens that are oriented to provideseveral unique display configurations. Further, the device can receiveuser input in unique ways. The overall design and functionality of thedevice provides for an enhanced user experience making the device moreuseful and more efficient.

Mechanical Features:

FIGS. 1A-1J illustrate a device 100 in accordance with embodiments ofthe present disclosure. As described in greater detail below, device 100can be positioned in a number of different ways each of which providesdifferent functionality to a user. The device 100 is a multi-screendevice that includes a primary screen 104 and a secondary screen 108,both of which are touch sensitive. In embodiments, the entire frontsurface of screens 104 and 108 may be touch sensitive and capable ofreceiving input by a user touching the front surface of the screens 104and 108. Primary screen 104 includes touch sensitive display 110, which,in addition to being touch sensitive, also displays information to auser. Secondary screen 108 includes touch sensitive display 114, whichalso displays information to a user. In other embodiments, screens 104and 108 may include more than one display area.

Primary screen 104 also includes a configurable area 112 that has beenconfigured for specific inputs when the user touches portions of theconfigurable area 112. Secondary screen 108 also includes a configurablearea 116 that has been configured for specific inputs. Areas 112 a and116 a have been configured to receive a “back” input indicating that auser would like to view information previously displayed. Areas 112 band 116 b have been configured to receive a “menu” input indicating thatthe user would like to view options from a menu. Areas 112 c and 116 chave been configured to receive a “home” input indicating that the userwould like to view information associated with a “home” view. In otherembodiments, areas 112 a-c and 116 a-c may be configured, in addition tothe configurations described above, for other types of specific inputsincluding controlling features of device 100, some non-limiting examplesincluding adjusting overall system power, adjusting the volume,adjusting the brightness, adjusting the vibration, selecting ofdisplayed items (on either of screen 104 or 108), operating a camera,operating a microphone, and initiating/terminating of telephone calls.Also, in some embodiments, areas 112 a-c and 116 a-c may be configuredfor specific inputs depending upon the application running on device 100and/or information displayed on touch sensitive displays 110 and/or 114.

In addition to touch sensing, primary screen 104 and secondary screen108 may also include areas that receive input from a user withoutrequiring the user to touch the display area of the screen. For example,primary screen 104 includes gesture capture area 120, and secondaryscreen 108 includes gesture capture area 124. These areas are able toreceive input by recognizing gestures made by a user without the needfor the user to actually touch the surface of the display area. Incomparison to touch sensitive displays 110 and 114, the gesture captureareas 120 and 124 are commonly not capable of rendering a displayedimage.

The two screens 104 and 108 are connected together with a hinge 128,shown clearly in FIG. 1C (illustrating a back view of device 100). Hinge128, in the embodiment shown in FIGS. 1A-1J, is a center hinge thatconnects screens 104 and 108 so that when the hinge is closed, screens104 and 108 are juxtaposed (i.e., side-by-side) as shown in FIG. 1B(illustrating a front view of device 100). Hinge 128 can be opened toposition the two screens 104 and 108 in different relative positions toeach other. As described in greater detail below, the device 100 mayhave different functionalities depending on the relative positions ofscreens 104 and 108.

FIG. 1D illustrates the right side of device 100. As shown in FIG. 1D,secondary screen 108 also includes a card slot 132 and a port 136 on itsside. Card slot 132 in embodiments, accommodates different types ofcards including a subscriber identity module (SIM). Port 136 inembodiments is an input/output port (I/O port) that allows device 100 tobe connected to other peripheral devices, such as a display, keyboard,or printing device. As can be appreciated, these are merely someexamples and in other embodiments device 100 may include other slots andports such as slots and ports for accommodating additional memorydevices and/or for connecting other peripheral devices. Also shown inFIG. 1D is an audio jack 140 that accommodates a tip, ring, sleeve (TRS)connector for example to allow a user to utilize headphones or aheadset.

Device 100 also includes a number of buttons 158. For example, FIG. 1Eillustrates the left side of device 100. As shown in FIG. 1E, the sideof primary screen 104 includes three buttons 144, 148, and 152, whichcan be configured for specific inputs. For example, buttons 144, 148,and 152 may be configured to, in combination or alone, control a numberof aspects of device 100. Some non-limiting examples include overallsystem power, volume, brightness, vibration, selection of displayeditems (on either of screen 104 or 108), a camera, a microphone, andinitiation/termination of telephone calls. In some embodiments, insteadof separate buttons two buttons may be combined into a rocker button.This arrangement is useful in situations where the buttons areconfigured to control features such as volume or brightness. In additionto buttons 144, 148, and 152, device 100 also includes a button 156,shown in FIG. 1F, which illustrates the top of device 100. In oneembodiment, button 156 is configured as an on/off button used to controloverall system power to device 100. In other embodiments, button 156 isconfigured to, in addition to or in lieu of controlling system power,control other aspects of device 100. In some embodiments, one or more ofthe buttons 144, 148, 152, and 156 are capable of supporting differentuser commands. By way of example, a normal press has a duration commonlyof less than about 1 second and resembles a quick tap. A medium presshas a duration commonly of 1 second or more but less than about 12seconds. A long press has a duration commonly of about 12 seconds ormore. The function of the buttons is normally specific to theapplication that is currently in focus on the respective display 110 and114. In a telephone application for instance and depending on theparticular button, a normal, medium, or long press can mean end call,increase in call volume, decrease in call volume, and toggle microphonemute. In a camera or video application for instance and depending on theparticular button, a normal, medium, or long press can mean increasezoom, decrease zoom, and take photograph or record video.

There are also a number of hardware components within device 100. Asillustrated in FIG. 1C, device 100 includes a speaker 160 and amicrophone 164. Device 100 also includes a camera 168 (FIG. 1B).Additionally, device 100 includes two position sensors 172A and 172B,which are used to determine the relative positions of screens 104 and108. In one embodiment, position sensors 172A and 172B are Hall effectsensors. However, in other embodiments other sensors can be used inaddition to or in lieu of the Hall effect sensors. An accelerometer 176may also be included as part of device 100 to determine the orientationof the device 100 and/or the orientation of screens 104 and 108.Additional internal hardware components that may be included in device100 are described below with respect to FIG. 2.

The overall design of device 100 allows it to provide additionalfunctionality not available in other communication devices. Some of thefunctionality is based on the various positions and orientations thatdevice 100 can have. As shown in FIGS. 1B-1G, device 100 can be operatedin an “open” position where screens 104 and 108 are juxtaposed. Thisposition allows a large display area for displaying information to auser. When position sensors 172A and 172B determine that device 100 isin the open position, they can generate a signal that can be used totrigger different events such as displaying information on both screens104 and 108. Additional events may be triggered if accelerometer 176determines that device 100 is in a portrait position (FIG. 1B) asopposed to a landscape position (not shown).

In addition to the open position, device 100 may also have a “closed”position illustrated in FIG. 1H. Again, position sensors 172A and 172Bcan generate a signal indicating that device 100 is in the “closed”position. This can trigger an event that results in a change ofdisplayed information on screen 104 and/or 108. For example, device 100may be programmed to stop displaying information on one of the screens,e.g., screen 108, since a user can only view one screen at a time whendevice 100 is in the “closed” position. In other embodiments, the signalgenerated by position sensors 172A and 172B, indicating that the device100 is in the “closed” position, can trigger device 100 to answer anincoming telephone call. The “closed” position can also be a preferredposition for utilizing the device 100 as a mobile phone.

Device 100 can also be used in an “easel” position which is illustratedin FIG. 1I. In the “easel” position, screens 104 and 108 are angled withrespect to each other and facing outward with the edges of screens 104and 108 substantially horizontal. In this position, device 100 can beconfigured to display information on both screens 104 and 108 to allowtwo users to simultaneously interact with device 100. When device 100 isin the “easel” position, sensors 172A and 172B generate a signalindicating that the screens 104 and 108 are positioned at an angle toeach other, and the accelerometer 176 can generate a signal indicatingthat device 100 has been placed so that the edge of screens 104 and 108are substantially horizontal. The signals can then be used incombination to generate events that trigger changes in the display ofinformation on screens 104 and 108.

FIG. 1J illustrates device 100 in a “modified easel” position. In the“modified easel” position, one of screens 104 or 108 is used as a standand is faced down on the surface of an object such as a table. Thisposition provides a convenient way for information to be displayed to auser in landscape orientation. Similar to the easel position, whendevice 100 is in the “modified easel” position, position sensors 172Aand 172B generate a signal indicating that the screens 104 and 108 arepositioned at an angle to each other. The accelerometer 176 wouldgenerate a signal indicating that device 100 has been positioned so thatone of screens 104 and 108 is faced downwardly and is substantiallyhorizontal. The signals can then be used to generate events that triggerchanges in the display of information of screens 104 and 108. Forexample, information may not be displayed on the screen that is facedown since a user cannot see the screen.

Transitional states are also possible. When the position sensors 172Aand B and/or accelerometer indicate that the screens are being closed orfolded (from open), a closing transitional state is recognized.Conversely when the position sensors 172A and B indicate that thescreens are being opened or folded (from closed), an openingtransitional state is recognized. The closing and opening transitionalstates are typically time-based, or have a maximum time duration from asensed starting point. Normally, no user input is possible when one ofthe closing and opening states is in effect. In this manner, incidentaluser contact with a screen during the closing or opening function is notmisinterpreted as user input. In embodiments, another transitional stateis possible when the device 100 is closed. This additional transitionalstate allows the display to switch from one screen 104 to the secondscreen 108 when the device 100 is closed based on some user input, e.g.,a double tap on the screen 110,114.

As can be appreciated, the description of device 100 is made forillustrative purposes only, and the embodiments are not limited to thespecific mechanical features shown in FIGS. 1A-1J and described above.In other embodiments, device 100 may include additional features,including one or more additional buttons, slots, display areas, hinges,and/or locking mechanisms. Additionally, in embodiments, the featuresdescribed above may be located in different parts of device 100 andstill provide similar functionality. Therefore, FIGS. 1A-1J and thedescription provided above are nonlimiting.

Hardware Features:

FIG. 2 illustrates components of a device 100 in accordance withembodiments of the present disclosure. In general, the device 100includes a primary screen 104 and a secondary screen 108. While theprimary screen 104 and its components are normally enabled in both theopened and closed positions or states, the secondary screen 108 and itscomponents are normally enabled in the opened state but disabled in theclosed state. However, even when in the closed state a user orapplication triggered interrupt (such as in response to a phoneapplication or camera application operation) can flip the active screen,or disable the primary screen 104 and enable the secondary screen 108,by a suitable command. Each screen 104, 108 can be touch sensitive andcan include different operative areas. For example, a first operativearea, within each touch sensitive screen 104 and 108, may comprise atouch sensitive display 110, 114. In general, the touch sensitivedisplay 110, 114 may comprise a full color, touch sensitive display. Asecond area within each touch sensitive screen 104 and 108 may comprisea gesture capture region 120, 124. The gesture capture region 120, 124may comprise an area or region that is outside of the touch sensitivedisplay 110, 114 area, and that is capable of receiving input, forexample in the form of gestures provided by a user. However, the gesturecapture region 120, 124 does not include pixels that can perform adisplay function or capability.

A third region of the touch sensitive screens 104 and 108 may comprise aconfigurable area 112, 116. The configurable area 112, 116 is capable ofreceiving input and has display or limited display capabilities. Inembodiments, the configurable area 112, 116 may present different inputoptions to the user. For example, the configurable area 112, 116 maydisplay buttons or other relatable items. Moreover, the identity ofdisplayed buttons, or whether any buttons are displayed at all withinthe configurable area 112, 116 of a touch sensitive screen 104 or 108,may be determined from the context in which the device 100 is usedand/or operated. In an exemplary embodiment, the touch sensitive screens104 and 108 comprise liquid crystal display devices extending across atleast those regions of the touch sensitive screens 104 and 108 that arecapable of providing visual output to a user, and a capacitive inputmatrix over those regions of the touch sensitive screens 104 and 108that are capable of receiving input from the user.

One or more display controllers 216 a, 216 b may be provided forcontrolling the operation of the touch sensitive screens 104 and 108,including input (touch sensing) and output (display) functions. In theexemplary embodiment illustrated in FIG. 2, a separate touch screencontroller 216 a or 216 b is provided for each touch screen 104 and 108.In accordance with alternate embodiments, a common or shared touchscreen controller 216 may be used to control each of the included touchsensitive screens 104 and 108. In accordance with still otherembodiments, the functions of a touch screen controller 216 a and/or 216b may be incorporated into other components, such as a processor 204.

The processor 204 may comprise a general purpose programmable processoror controller for executing application programming or instructions. Inaccordance with at least some embodiments, the processor 204 may includemultiple processor cores, and/or implement multiple virtual processors.In accordance with still other embodiments, the processor 204 mayinclude multiple physical processors. As a particular example, theprocessor 204 may comprise a specially configured application specificintegrated circuit (ASIC) or other integrated circuit, a digital signalprocessor, a controller, a hardwired electronic or logic circuit, aprogrammable logic device or gate array, a special purpose computer, orthe like. The processor 204 generally functions to run programming codeor instructions implementing various functions of the device 100.

A communication device 100 may also include memory 208 for use inconnection with the execution of application programming or instructionsby the processor 204, and for the temporary or long term storage ofprogram instructions and/or data. As examples, the memory 208 maycomprise RAM, DRAM, SDRAM, or other solid state memory. Alternatively orin addition, data storage 212 may be provided. Like the memory 208, thedata storage 212 may comprise a solid state memory device or devices.Alternatively or in addition, the data storage 212 may comprise a harddisk drive or other random access memory.

In support of communications functions or capabilities, the device 100can include a cellular telephony module 228. As examples, the cellulartelephony module 228 can comprise a GSM, CDMA, FDMA and/or analogcellular telephony transceiver capable of supporting voice, multimediaand/or data transfers over a cellular network. Alternatively or inaddition, the device 100 can include an additional or other wirelesscommunications module 232. As examples, the other wirelesscommunications module 232 can comprise a Wi-Fi, BLUETOOTH™, WiMax,infrared, or other wireless communications link. The cellular telephonymodule 228 and the other wireless communications module 232 can each beassociated with a shared or a dedicated antenna 224.

A port interface 252 may be included. The port interface 252 may includeproprietary or universal ports to support the interconnection of thedevice 100 to other devices or components, such as a dock, which may ormay not include additional or different capabilities from those integralto the device 100. In addition to supporting an exchange ofcommunication signals between the device 100 and another device orcomponent, the docking port 136 and/or port interface 252 can supportthe supply of power to or from the device 100. The port interface 252also comprises an intelligent element that comprises a docking modulefor controlling communications or other interactions between the device100 and a connected device or component.

An input/output module 248 and associated ports may be included tosupport communications over wired networks or links, for example withother communication devices, server devices, and/or peripheral devices.Examples of an input/output module 248 include an Ethernet port, aUniversal Serial Bus (USB) port, Institute of Electrical and ElectronicsEngineers (IEEE) 1394, or other interface.

An audio input/output interface/device(s) 244 can be included to provideanalog audio to an interconnected speaker or other device, and toreceive analog audio input from a connected microphone or other device.As an example, the audio input/output interface/device(s) 244 maycomprise an associated amplifier and analog to digital converter.Alternatively or in addition, the device 100 can include an integratedaudio input/output device 256 and/or an audio jack for interconnectingan external speaker or microphone. For example, an integrated speakerand an integrated microphone can be provided, to support near talk orspeaker phone operations.

Hardware buttons 158 can be included for example for use in connectionwith certain control operations. Examples include a master power switch,volume control, etc., as described in conjunction with FIGS. 1A through1J. One or more image capture interfaces/devices 240, such as a camera,can be included for capturing still and/or video images. Alternativelyor in addition, an image capture interface/device 240 can include ascanner or code reader. An image capture interface/device 240 caninclude or be associated with additional elements, such as a flash orother light source.

The device 100 can also include a global positioning system (GPS)receiver 236. In accordance with embodiments of the present invention,the GPS receiver 236 may further comprise a GPS module that is capableof providing absolute location information to other components of thedevice 100. An accelerometer(s) 176 may also be included. For example,in connection with the display of information to a user and/or otherfunctions, a signal from the accelerometer 176 can be used to determinean orientation and/or format in which to display that information to theuser.

Embodiments of the present invention can also include one or moreposition sensor(s) 172. The position sensor 172 can provide a signalindicating the position of the touch sensitive screens 104 and 108relative to one another. This information can be provided as an input,for example to a user interface application, to determine an operatingmode, characteristics of the touch sensitive displays 110, 114, and/orother device 100 operations. As examples, a screen position sensor 172can comprise a series of Hall effect sensors, a multiple positionswitch, an optical switch, a Wheatstone bridge, a potentiometer, orother arrangement capable of providing a signal indicating of multiplerelative positions the touch screens are in.

Communications between various components of the device 100 can becarried by one or more buses 222. In addition, power can be supplied tothe components of the device 100 from a power source and/or powercontrol module 260. The power control module 260 can, for example,include a battery, an AC to DC converter, power control logic, and/orports for interconnecting the device 100 to an external source of power.

Device State:

FIGS. 3A and 3B represent illustrative states of device 100. While anumber of illustrative states are shown, and transitions from a firststate to a second state, it is to be appreciated that the illustrativestate diagram may not encompass all possible states and/or all possibletransitions from a first state to a second state. As illustrated in FIG.3A, the various arrows between the states (illustrated by the staterepresented in the circle) represent a physical change that occurs tothe device 100, that is detected by one or more of hardware andsoftware, the detection triggering one or more of a hardware and/orsoftware interrupt that is used to control and/or manage one or morefunctions of device 100.

As illustrated in FIG. 3A, there are twelve exemplary “physical” states:closed 304, transition 308 (or opening transitional state), easel 312,modified easel 316, open 320, inbound/outbound call or communication324, image/video capture 328, transition 332 (or closing transitionalstate), landscape 340, docked 336, docked 344 and landscape 348. Next toeach illustrative state is a representation of the physical state of thedevice 100 with the exception of states 324 and 328, where the state isgenerally symbolized by the international icon for a telephone and theicon for a camera, respectfully.

In state 304, the device is in a closed state with the device 100generally oriented in the portrait direction with the primary screen 104and the secondary screen 108 back-to-back in different planes (see FIG.1H). From the closed state, the device 100 can enter, for example,docked state 336, where the device 100 is coupled with a dockingstation, docking cable, or in general docked or associated with one ormore other devices or peripherals, or the landscape state 340, where thedevice 100 is generally oriented with the primary screen 104 facing theuser, and the primary screen 104 and the secondary screen 108 beingback-to-back.

In the closed state, the device can also move to a transitional statewhere the device remains closed but the display is moved from one screen104 to another screen 108 based on a user input, e.g., a double tap onthe screen 110, 114. Still another embodiment includes a bilateralstate. In the bilateral state, the device remains closed, but a singleapplication displays at least one window on both the first display 110and the second display 114. The windows shown on the first and seconddisplay 110, 114 may be the same or different based on the applicationand the state of that application. For example, while acquiring an imagewith a camera, the device may display the view finder on the firstdisplay 110 and displays a preview for the photo subjects (full screenand mirrored left-to-right) on the second display 114.

In state 308, a transition state from the closed state 304 to thesemi-open state or easel state 312, the device 100 is shown opening withthe primary screen 104 and the secondary screen 108 being rotated arounda point of axis coincidence with the hinge. Upon entering the easelstate 312, the primary screen 104 and the secondary screen 108 areseparated from one another such that, for example, the device 100 cansit in an easel-like configuration on a surface.

In state 316, known as the modified easel position, the device 100 hasthe primary screen 104 and the secondary screen 108 in a similarrelative relationship to one another as in the easel state 312, with thedifference being one of the primary screen 104 or the secondary screen108 are placed on a surface as shown.

State 320 is the open state where the primary screen 104 and thesecondary screen 108 are generally on the same plane. From the openstate, the device 100 can transition to the docked state 344 or the openlandscape state 348. In the open state 320, the primary screen 104 andthe secondary screen 108 are generally in the portrait-like orientationwhile in landscaped state 348 the primary screen 104 and the secondaryscreen 108 are generally in a landscape-like orientation.

State 324 is illustrative of a communication state, such as when aninbound or outbound call is being received or placed, respectively, bythe device 100. While not illustrated for clarity, it should beappreciated the device 100 can transition to the inbound/outbound callstate 324 from any state illustrated in FIG. 3A. In a similar manner,the image/video capture state 328 can be entered into from any otherstate in FIG. 3A, with the image/video capture state 328 allowing thedevice 100 to take one or more images via a camera and/or videos with avideo capture device 240.

Transition state 332 illustratively shows primary screen 104 and thesecondary screen 108 being closed upon one another for entry into, forexample, the closed state 304.

FIG. 3B illustrates, with reference to the key, the inputs that arereceived to detect a transition from a first state to a second state. InFIG. 3B, various combinations of states are shown with in general, aportion of the columns being directed toward a portrait state 352, alandscape state 356, and a portion of the rows being directed toportrait state 360 and landscape state 364.

In FIG. 3B, the Key indicates that “H” represents an input from one ormore Hall Effect sensors, “A” represents an input from one or moreaccelerometers, “T” represents an input from a timer, “P” represents acommunications trigger input and “I” represents an image and/or videocapture request input. Thus, in the center portion 376 of the chart, aninput, or combination of inputs, are shown that represent how the device100 detects a transition from a first physical state to a secondphysical state.

As discussed, in the center portion of the chart 376, the inputs thatare received enable the detection of a transition from, for example, aportrait open state to a landscape easel state—shown in bold—“HAT.” Forthis exemplary transition from the portrait open to the landscape easelstate, a Hall Effect sensor (“H”), an accelerometer (“A”) and a timer(“T”) input may be needed. The timer input can be derived from, forexample, a clock associated with the processor.

In addition to the portrait and landscape states, a docked state 368 isalso shown that is triggered based on the receipt of a docking signal372. As discussed above and in relation to FIG. 3, the docking signalcan be triggered by the association of the device 100 with one or moreother device 100s, accessories, peripherals, smart docks, or the like.

User Interaction:

FIGS. 4A through 4H depict various graphical representations of gestureinputs that may be recognized by the screens 104, 108. The gestures maybe performed not only by a user's body part, such as a digit, but alsoby other devices, such as a stylus, that may be sensed by the contactsensing portion(s) of a screen 104, 108. In general, gestures areinterpreted differently, based on where the gestures are performed(either directly on the display 110, 114 or in the gesture captureregion 120, 124). For example, gestures in the display 110,114 may bedirected to a desktop or application, and gestures in the gesturecapture region 120, 124 may be interpreted as for the system.

With reference to FIGS. 4A-4H, a first type of gesture, a touch gesture420, is substantially stationary on the screen 104,108 for a selectedlength of time. A circle 428 represents a touch or other contact typereceived at particular location of a contact sensing portion of thescreen. The circle 428 may include a border 432, the thickness of whichindicates a length of time that the contact is held substantiallystationary at the contact location. For instance, a tap 420 (or shortpress) has a thinner border 432 a than the border 432 b for a long press424 (or for a normal press). The long press 424 may involve a contactthat remains substantially stationary on the screen for longer timeperiod than that of a tap 420. As will be appreciated, differentlydefined gestures may be registered depending upon the length of timethat the touch remains stationary prior to contact cessation or movementon the screen.

With reference to FIG. 4C, a drag gesture 400 on the screen 104,108 isan initial contact (represented by circle 428) with contact movement 436in a selected direction. The initial contact 428 may remain stationaryon the screen 104,108 for a certain amount of time represented by theborder 432. The drag gesture typically requires the user to contact anicon, window, or other displayed image at a first location followed bymovement of the contact in a drag direction to a new second locationdesired for the selected displayed image. The contact movement need notbe in a straight line but have any path of movement so long as thecontact is substantially continuous from the first to the secondlocations.

With reference to FIG. 4D, a flick gesture 404 on the screen 104,108 isan initial contact (represented by circle 428) with truncated contactmovement 436 (relative to a drag gesture) in a selected direction. Inembodiments, a flick has a higher exit velocity for the last movement inthe gesture compared to the drag gesture. The flick gesture can, forinstance, be a finger snap following initial contact. Compared to a draggesture, a flick gesture generally does not require continual contactwith the screen 104,108 from the first location of a displayed image toa predetermined second location. The contacted displayed image is movedby the flick gesture in the direction of the flick gesture to thepredetermined second location. Although both gestures commonly can movea displayed image from a first location to a second location, thetemporal duration and distance of travel of the contact on the screen isgenerally less for a flick than for a drag gesture.

With reference to FIG. 4E, a pinch gesture 408 on the screen 104,108 isdepicted. The pinch gesture 408 may be initiated by a first contact 428to the screen 104,108 by, for example, a first digit and a secondcontact 428 b to the screen 104,108 by, for example, a second digit. Thefirst and second contacts 428 a,b may be detected by a common contactsensing portion of a common screen 104,108, by different contact sensingportions of a common screen 104 or 108, or by different contact sensingportions of different screens. The first contact 428 a is held for afirst amount of time, as represented by the border 432 a, and the secondcontact 428 b is held for a second amount of time, as represented by theborder 432 b. The first and second amounts of time are generallysubstantially the same, and the first and second contacts 428 a, bgenerally occur substantially simultaneously. The first and secondcontacts 428 a, b generally also include corresponding first and secondcontact movements 436 a, b, respectively. The first and second contactmovements 436 a, b are generally in opposing directions. Stated anotherway, the first contact movement 436 a is towards the second contact 436b, and the second contact movement 436 b is towards the first contact436 a. More simply stated, the pinch gesture 408 may be accomplished bya user's digits touching the screen 104,108 in a pinching motion.

With reference to FIG. 4F, a spread gesture 410 on the screen 104,108 isdepicted. The spread gesture 410 may be initiated by a first contact 428a to the screen 104,108 by, for example, a first digit and a secondcontact 428 b to the screen 104,108 by, for example, a second digit. Thefirst and second contacts 428 a,b may be detected by a common contactsensing portion of a common screen 104,108, by different contact sensingportions of a common screen 104,108, or by different contact sensingportions of different screens. The first contact 428 a is held for afirst amount of time, as represented by the border 432 a, and the secondcontact 428 b is held for a second amount of time, as represented by theborder 432 b. The first and second amounts of time are generallysubstantially the same, and the first and second contacts 428 a, bgenerally occur substantially simultaneously. The first and secondcontacts 428 a, b generally also include corresponding first and secondcontact movements 436 a, b, respectively. The first and second contactmovements 436 a, b are generally in a common direction. Stated anotherway, the first and second contact movements 436 a, b are away from thefirst and second contacts 428 a, b. More simply stated, the spreadgesture 410 may be accomplished by a user's digits touching the screen104,108 in a spreading motion.

The above gestures may be combined in any manner, such as those shown byFIGS. 4G and 4H, to produce a determined functional result. For example,in FIG. 4G a tap gesture 420 is combined with a drag or flick gesture412 in a direction away from the tap gesture 420. In FIG. 4H, a tapgesture 420 is combined with a drag or flick gesture 412 in a directiontowards the tap gesture 420.

The functional result of receiving a gesture can vary depending on anumber of factors, including a state of the device 100, display 110,114, or screen 104, 108, a context associated with the gesture, orsensed location of the gesture. The state of the device commonly refersto one or more of a configuration of the device 100, a displayorientation, and user and other inputs received by the device 100.Context commonly refers to one or more of the particular application(s)selected by the gesture and the portion(s) of the application currentlyexecuting, whether the application is a single- or multi-screenapplication, and whether the application is a multi-screen applicationdisplaying one or more windows in one or more screens or in one or morestacks. Sensed location of the gesture commonly refers to whether thesensed set(s) of gesture location coordinates are on a touch sensitivedisplay 110, 114 or a gesture capture region 120, 124, whether thesensed set(s) of gesture location coordinates are associated with acommon or different display or screen 104,108, and/or what portion ofthe gesture capture region contains the sensed set(s) of gesturelocation coordinates.

A tap, when received by an a touch sensitive display 110, 114, can beused, for instance, to select an icon to initiate or terminate executionof a corresponding application, to maximize or minimize a window, toreorder windows in a stack, and to provide user input such as bykeyboard display or other displayed image. A drag, when received by atouch sensitive display 110, 114, can be used, for instance, to relocatean icon or window to a desired location within a display, to reorder astack on a display, or to span both displays (such that the selectedwindow occupies a portion of each display simultaneously). A flick, whenreceived by a touch sensitive display 110, 114 or a gesture captureregion 120, 124, can be used to relocate a window from a first displayto a second display or to span both displays (such that the selectedwindow occupies a portion of each display simultaneously). Unlike thedrag gesture, however, the flick gesture is generally not used to movethe displayed image to a specific user-selected location but to adefault location that is not configurable by the user.

The pinch gesture, when received by a touch sensitive display 110, 114or a gesture capture region 120, 124, can be used to minimize orotherwise increase the displayed area or size of a window (typicallywhen received entirely by a common display), to switch windows displayedat the top of the stack on each display to the top of the stack of theother display (typically when received by different displays orscreens), or to display an application manager (a “pop-up window” thatdisplays the windows in the stack). The spread gesture, when received bya touch sensitive display 110, 114 or a gesture capture region 120, 124,can be used to maximize or otherwise decrease the displayed area or sizeof a window, to switch windows displayed at the top of the stack on eachdisplay to the top of the stack of the other display (typically whenreceived by different displays or screens), or to display an applicationmanager (typically when received by an off-screen gesture capture regionon the same or different screens).

The combined gestures of FIG. 4G, when received by a common displaycapture region in a common display or screen 104,108, can be used tohold a first window stack location in a first stack constant for adisplay receiving the gesture while reordering a second window stacklocation in a second window stack to include a window in the displayreceiving the gesture. The combined gestures of FIG. 4H, when receivedby different display capture regions in a common display or screen104,108 or in different displays or screens, can be used to hold a firstwindow stack location in a first window stack constant for a displayreceiving the tap part of the gesture while reordering a second windowstack location in a second window stack to include a window in thedisplay receiving the flick or drag gesture. Although specific gesturesand gesture capture regions in the preceding examples have beenassociated with corresponding sets of functional results, it is to beappreciated that these associations can be redefined in any manner toproduce differing associations between gestures and/or gesture captureregions and/or functional results.

Firmware and Software:

The memory 508 may store and the processor 504 may execute one or moresoftware components. These components can include at least one operatingsystem (OS) 516, an application manager 562, a desktop 566, and/or oneor more applications 564 a and/or 564 b from an application store 560.The OS 516 can include a framework 520, one or more frame buffers 548,one or more drivers 512, previously described in conjunction with FIG.2, and/or a kernel 518. The OS 516 can be any software, consisting ofprograms and data, which manages computer hardware resources andprovides common services for the execution of various applications 564.The OS 516 can be any operating system and, at least in someembodiments, dedicated to mobile devices, including, but not limited to,Linux, ANDROID™, iPhone OS (IOS™), WINDOWS PHONE 7™, etc. The OS 516 isoperable to provide functionality to the phone by executing one or moreoperations, as described herein.

The applications 564 can be any higher level software that executesparticular functionality for the user. Applications 564 can includeprograms such as email clients, web browsers, texting applications,games, media players, office suites, etc. The applications 564 can bestored in an application store 560, which may represent any memory ordata storage, and the management software associated therewith, forstoring the applications 564. Once executed, the applications 564 may berun in a different area of memory 508.

The framework 520 may be any software or data that allows the multipletasks running on the device to interact. In embodiments, at leastportions of the framework 520 and the discrete components describedhereinafter may be considered part of the OS 516 or an application 564.However, these portions will be described as part of the framework 520,but those components are not so limited. The framework 520 can include,but is not limited to, a Multi-Display Management (MDM) module 524, aSurface Cache module 528, a Window Management module 532, an InputManagement module 536, a Task Management module 540, an ApplicationModel Manager 542, a Display Controller, one or more frame buffers 548,a task stack 552, one or more window stacks 550 (which is a logicalarrangement of windows and/or desktops in a display area), and/or anevent buffer 556.

The MDM module 524 includes one or more modules that are operable tomanage the display of applications or other data on the screens of thedevice. An embodiment of the MDM module 524 is described in conjunctionwith FIG. 5B. In embodiments, the MDM module 524 receives inputs fromthe other OS 516 components, such as, the drivers 512, and from theapplications 564 to determine continually the state of the device 100.The inputs assist the MDM module 524 in determining how to configure andallocate the displays according to the application's preferences andrequirements, and the user's actions. Once a determination for displayconfigurations is made, the MDM module 524 can bind the applications 564to a display. The configuration may then be provided to one or moreother components to generate a window with a display.

The Surface Cache module 528 includes any memory or storage and thesoftware associated therewith to store or cache one or more images ofwindows. A series of active and/or non-active windows (or other displayobjects, such as, a desktop display) can be associated with eachdisplay. An active window (or other display object) is currentlydisplayed. A non-active windows (or other display objects) were openedand, at some time, displayed but are now not displayed. To enhance theuser experience, before a window transitions from an active state to aninactive state, a “screen shot” of a last generated image of the window(or other display object) can be stored. The Surface Cache module 528may be operable to store a bitmap of the last active image of a window(or other display object) not currently displayed. Thus, the SurfaceCache module 528 stores the images of non-active windows (or otherdisplay objects) in a data store.

In embodiments, the Window Management module 532 is operable to managethe windows (or other display objects) that are active or not active oneach of the displays. The Window Management module 532, based oninformation from the MDM module 524, the OS 516, or other components,determines when a window (or other display object) is visible or notactive. The Window Management module 532 may then put a non-visiblewindow (or other display object) in a “not active state” and, inconjunction with the Task Management module Task Management 540 suspendsthe application's operation. Further, the Window Management module 532may assign, through collaborative interaction with the MDM module 524, adisplay identifier to the window (or other display object) or manage oneor more other items of data associated with the window (or other displayobject). The Window Management module 532 may also provide the storedinformation to the application 564, the Task Management module 540, orother components interacting with or associated with the window (orother display object). The Window Management module 532 can alsoassociate an input task with a window based on window focus and displaycoordinates within the motion space.

The Input Management module 536 is operable to manage events that occurwith the device. An event is any input into the window environment, forexample, a user interface interactions with a user. The Input Managementmodule 536 receives the events and logically stores the events in anevent buffer 556. Events can include such user interface interactions asa “down event,” which occurs when a screen 104, 108 receives a touchsignal from a user, a “move event,” which occurs when the screen 104,108 determines that a user's finger is moving across a screen(s), an “upevent, which occurs when the screen 104, 108 determines that the userhas stopped touching the screen 104, 108, etc. These events arereceived, stored, and forwarded to other modules by the Input Managementmodule 536. The Input Management module 536 may also map screen inputsto a motion space which is the culmination of all physical and virtualdisplay available on the device.

The motion space is a virtualized space that includes all touchsensitive displays 110,114 “tiled” together to mimic the physicaldimensions of the device 100. For example, when the device 100 isunfolded, the motion space size may be 960×800, which may be the numberof pixels in the combined display area for both touch sensitive displays110, 114. If a user touches on a first touch sensitive display 110 onlocation (40, 40), a full screen window can receive touch event withlocation (40, 40). If a user touches on a second touch sensitive display114, with location (40, 40), the full screen window can receive touchevent with location (520, 40), because the second touch sensitivedisplay 114 is on the right side of the first touch sensitive display110, so the device 100 can offset the touch by the first touch sensitivedisplay's 110 width, which is 480 pixels. When a hardware event occurswith location info from a driver 512, the framework 520 can up-scale thephysical location to the motion space because the location of the eventmay be different based on the device orientation and state. The motionspace may be as described in U.S. patent application Ser. No.13/187,026, filed Jul. 20, 2011, entitled “Systems and Methods forReceiving Gesture Inputs Spanning Multiple Input Devices,” which ishereby incorporated by reference in its entirety for all that it teachesand for all purposes.

A task can be an application and a sub-task can be an applicationcomponent that provides a window with which users can interact to dosomething, such as dial the phone, take a photo, send an email, or viewa map. Each task may be given a window in which to draw a userinterface. The window typically fills a display (for example, touchsensitive display 110,114), but may be smaller than the display 110,114and float on top of other windows. An application usually consists ofmultiple sub-tasks that are loosely bound to each other. Typically, onetask in an application is specified as the “main” task, which ispresented to the user when launching the application for the first time.Each task can then start another task or sub-task to perform differentactions.

The Task Management module 540 is operable to manage the operation ofone or more applications 564 that may be executed by the device. Thus,the Task Management module 540 can receive signals to launch, suspend,terminate, etc. an application or application sub-tasks stored in theapplication store 560. The Task Management module 540 may theninstantiate one or more tasks or sub-tasks of the application 564 tobegin operation of the application 564. Further, the Task ManagementModule 540 may launch, suspend, or terminate a task or sub-task as aresult of user input or as a result of a signal from a collaboratingframework 520 component. The Task Management Module 540 is responsiblefor managing the lifecycle of applications (tasks and sub-task) fromwhen the application is launched to when the application is terminated.

The processing of the Task Management Module 540 is facilitated by atask stack 552, which is a logical structure associated with the TaskManagement Module 540. The task stack 552 maintains the state of alltasks and sub-tasks on the device 100. When some component of theoperating system 516 requires a task or sub-task to transition in itslifecycle, the OS 516 component can notify the Task Management Module540. The Task Management Module 540 may then locate the task orsub-task, using identification information, in the task stack 552, andsend a signal to the task or sub-task indicating what kind of lifecycletransition the task needs to execute. Informing the task or sub-task ofthe transition allows the task or sub-task to prepare for the lifecyclestate transition. The Task Management Module 540 can then execute thestate transition for the task or sub-task. In embodiments, the statetransition may entail triggering the OS kernel 518 to terminate the taskwhen termination is required.

Further, the Task Management module 540 may suspend the application 564based on information from the Window Management Module 532. Suspendingthe application 564 may maintain application data in memory but maylimit or stop the application 564 from rendering a window or userinterface. Once the application becomes active again, the TaskManagement module 540 can again trigger the application to render itsuser interface. In embodiments, if a task is suspended, the task maysave the task's state in case the task is terminated. In the suspendedstate, the application task may not receive input because theapplication window is not visible to the user.

The frame buffer 548 is a logical structure(s) used to render the userinterface. The frame buffer 548 can be created and destroyed by the OSkernel 518. However, the Display Controller 544 can write the imagedata, for the visible windows, into the frame buffer 548. A frame buffer548 can be associated with one screen or multiple screens. Theassociation of a frame buffer 548 with a screen can be controlleddynamically by interaction with the OS kernel 518. A composite displaymay be created by associating multiple screens with a single framebuffer 548. Graphical data used to render an application's window userinterface may then be written to the single frame buffer 548, for thecomposite display, which is output to the multiple screens 104,108. TheDisplay Controller 544 can direct an application's user interface to aportion of the frame buffer 548 that is mapped to a particular display110,114, thus, displaying the user interface on only one screen 104 or108. The Display Controller 544 can extend the control over userinterfaces to multiple applications, controlling the user interfaces foras many displays as are associated with a frame buffer 548 or a portionthereof. This approach compensates for the multiple physical screens104,108 that are in use by the software component above the DisplayController 544.

The Application Manager 562 is an application that provides apresentation layer for the window environment. Thus, the ApplicationManager 562 provides the graphical model for rendering by the TaskManagement Module 540. Likewise, the Desktop 566 provides thepresentation layer for the Application Store 560. Thus, the desktopprovides a graphical model of a surface having selectable applicationicons for the Applications 564 in the Application Store 560 that can beprovided to the Window Management Module 556 for rendering.

Further, the framework can include an Application Model Manager (AMM)542. The Application Manager 562 may interface with the AMM 542. Inembodiments, the AMM 542 receives state change information from thedevice 100 regarding the state of applications (which are running orsuspended). The AMM 542 can associate bit map images from the SurfaceCache Module 528 to the tasks that are alive (running or suspended).Further, the AMM 542 can convert the logical window stack maintained inthe Task Manager Module 540 to a linear (“film strip” or “deck ofcards”) organization that the user perceives when the using the offgesture capture area 120 to sort through the windows. Further, the AMM542 may provide a list of executing applications to the ApplicationManager 562.

An embodiment of the MDM module 524 is shown in FIG. 5B. The MDM module524 is operable to determine the state of the environment for thedevice, including, but not limited to, the orientation of the device,whether the device 100 is opened or closed, what applications 564 areexecuting, how the applications 564 are to be displayed, what actionsthe user is conducting, the tasks being displayed, etc. To configure thedisplay, the MDM module 524 interprets these environmental factors anddetermines a display configuration, as described in conjunction withFIGS. 6A-6J. Then, the MDM module 524 can bind the applications 564 orother device components to the displays. The configuration may then besent to the Display Controller 544 and/or the other components withinthe OS 516 to generate the display. The MDM module 524 can include oneor more of, but is not limited to, a Display Configuration Module 568, aPreferences Module 572, a Device State Module 574, a Gesture Module 576,a Requirements Module 580, an Event Module 584, and/or a Binding Module588.

The Display Configuration Module 568 determines the layout for thedisplay. In embodiments, the Display Configuration Module 568 candetermine the environmental factors. The environmental factors may bereceived from one or more other MDM modules 524 or from other sources.The Display Configuration Module 568 can then determine from the list offactors the best configuration for the display. Some embodiments of thepossible configurations and the factors associated therewith aredescribed in conjunction with FIGS. 6A-6F.

The Preferences Module 572 is operable to determine display preferencesfor an application 564 or other component. For example, an applicationcan have a preference for Single or Dual displays. The PreferencesModule 572 can determine an application's display preference (e.g., byinspecting the application's preference settings) and may allow theapplication 564 to change to a mode (e.g., single screen, dual screen,max, etc.) if the device 100 is in a state that can accommodate thepreferred mode. However, some user interface policies may disallow amode even if the mode is available. As the configuration of the devicechanges, the preferences may be reviewed to determine if a betterdisplay configuration can be achieved for an application 564.

The Device State Module 574 is operable to determine or receive thestate of the device. The state of the device can be as described inconjunction with FIGS. 3A and 3B. The state of the device can be used bythe Display Configuration Module 568 to determine the configuration forthe display. As such, the Device State Module 574 may receive inputs andinterpret the state of the device. The state information is thenprovided to the Display Configuration Module 568.

The Gesture Module 576 is shown as part of the MDM module 524, but, inembodiments, the Gesture module 576 may be a separate Framework 520component that is separate from the MDM module 524. In embodiments, theGesture Module 576 is operable to determine if the user is conductingany actions on any part of the user interface. In alternativeembodiments, the Gesture Module 576 receives user interface actions fromthe configurable area 112,116 only. The Gesture Module 576 can receivetouch events that occur on the configurable area 112,116 (or possiblyother user interface areas) by way of the Input Management Module 536and may interpret the touch events (using direction, speed, distance,duration, and various other parameters) to determine what kind ofgesture the user is performing. When a gesture is interpreted, theGesture Module 576 can initiate the processing of the gesture and, bycollaborating with other Framework 520 components, can manage therequired window animation. The Gesture Module 576 collaborates with theApplication Model Manager 542 to collect state information with respectto which applications are running (active or paused) and the order inwhich applications must appear when a user gesture is performed. TheGesture Module 576 may also receive references to bitmaps (from theSurface Cache Module 528) and live windows so that when a gesture occursit can instruct the Display Controller 544 how to move the window(s)across the display 110,114. Thus, suspended applications may appear tobe running when those windows are moved across the display 110,114.

Further, the Gesture Module 576 can receive task information either fromthe Task Manage Module 540 or the Input Management module 536. Thegestures may be as defined in conjunction with FIGS. 4A through 4H. Forexample, moving a window causes the display to render a series ofdisplay frames that illustrate the window moving. The gesture associatedwith such user interface interaction can be received and interpreted bythe Gesture Module 576. The information about the user gesture is thensent to the Task Management Module 540 to modify the display binding ofthe task.

The Requirements Module 580, similar to the Preferences Module 572, isoperable to determine display requirements for an application 564 orother component. An application can have a set display requirement thatmust be observed. Some applications require a particular displayorientation. For example, the application “Angry Birds” can only bedisplayed in landscape orientation. This type of display requirement canbe determined or received, by the Requirements Module 580. As theorientation of the device changes, the Requirements Module 580 canreassert the display requirements for the application 564. The DisplayConfiguration Module 568 can generate a display configuration that is inaccordance with the application display requirements, as provided by theRequirements Module 580.

The Event Module 584, similar to the Gesture Module 576, is operable todetermine one or more events occurring with an application or othercomponent that can affect the user interface. Thus, the Event Module 584can receive event information either from the event buffer 556 or theTask Management module 540. These events can change how the tasks arebound to the displays. The Event Module 584 can collect state changeinformation from other Framework 520 components and act upon that statechange information. In an example, when the phone is opened or closed orwhen an orientation change has occurred, a new message may be renderedin a secondary screen. The state change based on the event can bereceived and interpreted by the Event Module 584. The information aboutthe events then may be sent to the Display Configuration Module 568 tomodify the configuration of the display.

The Binding Module 588 is operable to bind the applications 564 or theother components to the configuration determined by the DisplayConfiguration Module 568. A binding associates, in memory, the displayconfiguration for each application with the display and mode of theapplication. Thus, the Binding Module 588 can associate an applicationwith a display configuration for the application (e.g. landscape,portrait, multi-screen, etc.). Then, the Binding Module 588 may assign adisplay identifier to the display. The display identifier associated theapplication with a particular display of the device 100. This binding isthen stored and provided to the Display Controller 544, the othercomponents of the OS 516, or other components to properly render thedisplay. The binding is dynamic and can change or be updated based onconfiguration changes associated with events, gestures, state changes,application preferences or requirements, etc.

User Interface Configurations:

With reference now to FIGS. 6A-J, various types of output configurationsmade possible by the device 100 will be described hereinafter.

FIGS. 6A and 6B depict two different output configurations of the device100 being in a first state. Specifically, FIG. 6A depicts the device 100being in a closed portrait state 304 where the data is displayed on theprimary screen 104. In this example, the device 100 displays data viathe touch sensitive display 110 in a first portrait configuration 604.As can be appreciated, the first portrait configuration 604 may onlydisplay a desktop or operating system home screen. Alternatively, one ormore windows may be presented in a portrait orientation while the device100 is displaying data in the first portrait configuration 604.

FIG. 6B depicts the device 100 still being in the closed portrait state304, but instead data is displayed on the secondary screen 108. In thisexample, the device 100 displays data via the touch sensitive display114 in a second portrait configuration 608.

It may be possible to display similar or different data in either thefirst or second portrait configuration 604, 608. It may also be possibleto transition between the first portrait configuration 604 and secondportrait configuration 608 by providing the device 100 a user gesture(e.g., a double tap gesture), a menu selection, or other means. Othersuitable gestures may also be employed to transition betweenconfigurations. Furthermore, it may also be possible to transition thedevice 100 from the first or second portrait configuration 604, 608 toany other configuration described herein depending upon which state thedevice 100 is moved.

An alternative output configuration may be accommodated by the device100 being in a second state. Specifically, FIG. 6C depicts a thirdportrait configuration where data is displayed simultaneously on boththe primary screen 104 and the secondary screen 108. The third portraitconfiguration may be referred to as a Dual-Portrait (PD) outputconfiguration. In the PD output configuration, the touch sensitivedisplay 110 of the primary screen 104 depicts data in the first portraitconfiguration 604 while the touch sensitive display 114 of the secondaryscreen 108 depicts data in the second portrait configuration 608. Thesimultaneous presentation of the first portrait configuration 604 andthe second portrait configuration 608 may occur when the device 100 isin an open portrait state 320. In this configuration, the device 100 maydisplay one application window in one display 110 or 114, twoapplication windows (one in each display 110 and 114), one applicationwindow and one desktop, or one desktop. Other configurations may bepossible. It should be appreciated that it may also be possible totransition the device 100 from the simultaneous display ofconfigurations 604, 608 to any other configuration described hereindepending upon which state the device 100 is moved. Furthermore, whilein this state, an application's display preference may place the deviceinto bilateral mode, in which both displays are active to displaydifferent windows in the same application. For example, a Cameraapplication may display a viewfinder and controls on one side, while theother side displays a mirrored preview that can be seen by the photosubjects. Games involving simultaneous play by two players may also takeadvantage of bilateral mode.

FIGS. 6D and 6E depicts two further output configurations of the device100 being in a third state. Specifically, FIG. 6D depicts the device 100being in a closed landscape state 340 where the data is displayed on theprimary screen 104. In this example, the device 100 displays data viathe touch sensitive display 110 in a first landscape configuration 612.Much like the other configurations described herein, the first landscapeconfiguration 612 may display a desktop, a home screen, one or morewindows displaying application data, or the like.

FIG. 6E depicts the device 100 still being in the closed landscape state340, but instead data is displayed on the secondary screen 108. In thisexample, the device 100 displays data via the touch sensitive display114 in a second landscape configuration 616. It may be possible todisplay similar or different data in either the first or second portraitconfiguration 612, 616. It may also be possible to transition betweenthe first landscape configuration 612 and second landscape configuration616 by providing the device 100 with one or both of a twist and tapgesture or a flip and slide gesture. Other suitable gestures may also beemployed to transition between configurations. Furthermore, it may alsobe possible to transition the device 100 from the first or secondlandscape configuration 612, 616 to any other configuration describedherein depending upon which state the device 100 is moved.

FIG. 6F depicts a third landscape configuration where data is displayedsimultaneously on both the primary screen 104 and the secondary screen108. The third landscape configuration may be referred to as aDual-Landscape (LD) output configuration. In the LD outputconfiguration, the touch sensitive display 110 of the primary screen 104depicts data in the first landscape configuration 612 while the touchsensitive display 114 of the secondary screen 108 depicts data in thesecond landscape configuration 616. The simultaneous presentation of thefirst landscape configuration 612 and the second landscape configuration616 may occur when the device 100 is in an open landscape state 340. Itshould be appreciated that it may also be possible to transition thedevice 100 from the simultaneous display of configurations 612, 616 toany other configuration described herein depending upon which state thedevice 100 is moved.

FIGS. 6G and 6H depict two views of a device 100 being in yet anotherstate. Specifically, the device 100 is depicted as being in an easelstate 312. FIG. 6G shows that a first easel output configuration 618 maybe displayed on the touch sensitive display 110. FIG. 6H shows that asecond easel output configuration 620 may be displayed on the touchsensitive display 114. The device 100 may be configured to depict eitherthe first easel output configuration 618 or the second easel outputconfiguration 620 individually. Alternatively, both the easel outputconfigurations 618, 620 may be presented simultaneously. In someembodiments, the easel output configurations 618, 620 may be similar oridentical to the landscape output configurations 612, 616. The device100 may also be configured to display one or both of the easel outputconfigurations 618, 620 while in a modified easel state 316. It shouldbe appreciated that simultaneous utilization of the easel outputconfigurations 618, 620 may facilitate two-person games (e.g.,Battleship®, chess, checkers, etc.), multi-user conferences where two ormore users share the same device 100, and other applications. As can beappreciated, it may also be possible to transition the device 100 fromthe display of one or both configurations 618, 620 to any otherconfiguration described herein depending upon which state the device 100is moved.

FIG. 6I depicts yet another output configuration that may beaccommodated while the device 100 is in an open portrait state 320.Specifically, the device 100 may be configured to present a singlecontinuous image across both touch sensitive displays 110, 114 in aportrait configuration referred to herein as a Portrait-Max (PMax)configuration 624. In this configuration, data (e.g., a single image,application, window, icon, video, etc.) may be split and displayedpartially on one of the touch sensitive displays while the other portionof the data is displayed on the other touch sensitive display. The Pmaxconfiguration 624 may facilitate a larger display and/or betterresolution for displaying a particular image on the device 100. Similarto other output configurations, it may be possible to transition thedevice 100 from the Pmax configuration 624 to any other outputconfiguration described herein depending upon which state the device 100is moved.

FIG. 6J depicts still another output configuration that may beaccommodated while the device 100 is in an open landscape state 348.Specifically, the device 100 may be configured to present a singlecontinuous image across both touch sensitive displays 110, 114 in alandscape configuration referred to herein as a Landscape-Max (LMax)configuration 628. In this configuration, data (e.g., a single image,application, window, icon, video, etc.) may be split and displayedpartially on one of the touch sensitive displays while the other portionof the data is displayed on the other touch sensitive display. The Lmaxconfiguration 628 may facilitate a larger display and/or betterresolution for displaying a particular image on the device 100. Similarto other output configurations, it may be possible to transition thedevice 100 from the Lmax configuration 628 to any other outputconfiguration described herein depending upon which state the device 100is moved.

The device 100 manages desktops and/or windows with at least one windowstack 1700, 1728, as shown in FIGS. 9A and 9B. A window stack 1700, 1728is a logical arrangement of active and/or inactive windows for amulti-screen device. For example, the window stack 1700, 1728 may belogically similar to a deck of cards, where one or more windows ordesktops are arranged in order, as shown in FIGS. 9A and 9B. An activewindow is a window that is currently being displayed on at least one ofthe touch sensitive displays 110, 114. For example, windows 104 and 108are active windows and are displayed on touch sensitive displays 110 and114. An inactive window is a window that was opened and displayed but isnow “behind” an active window and not being displayed. In embodiments,an inactive window may be for an application that is suspended, andthus, the window is not displaying active content. For example, windows1712, 1716, 1720, and 1724 are inactive windows.

A window stack 1700, 1728 may have various arrangements ororganizational structures. In the embodiment shown in FIG. 9A, thedevice 100 includes a first stack 1760 associated with a first touchsensitive display 110 and a second stack associated with a second touchsensitive display 114. Thus, each touch sensitive display 110, 114 canhave an associated window stack 1760, 1764. These two window stacks1760, 1764 may have different numbers of windows arranged in therespective stacks 1760, 1764. Further, the two window stacks 1760, 1764can also be identified differently and managed separately. Thus, thefirst window stack 1760 can be arranged in order from a first window1704 to a next window 1720 to a last window 1724 and finally to adesktop 1722, which, in embodiments, is at the “bottom” of the windowstack 1760. In embodiments, the desktop 1722 is not always at the“bottom” as application windows can be arranged in the window stackbelow the desktop 1722, and the desktop 1722 can be brought to the “top”of a stack over other windows during a desktop reveal. Likewise, thesecond stack 1764 can be arranged from a first window 1708 to a nextwindow 1712 to a last window 1716, and finally to a desktop 1718, which,in embodiments, is a single desktop area, with desktop 1722, under allthe windows in both window stack 1760 and window stack 1764. A logicaldata structure for managing the two window stacks 1760, 1764 may be asdescribed in conjunction with FIG. 10.

Another arrangement for a window stack 1728 is shown in FIG. 9B. In thisembodiment, there is a single window stack 1728 for both touch sensitivedisplays 110, 114. Thus, the window stack 1728 is arranged from adesktop 1758 to a first window 1744 to a last window 1756. A window canbe arranged in a position among all windows without an association to aspecific touch sensitive display 110, 114. In this embodiment, a windowis in the order of windows. Further, at least one window is identifiedas being active. For example, a single window may be rendered in twoportions 1732 and 1736 that are displayed on the first touch sensitivescreen 110 and the second touch sensitive screen 114. The single windowmay only occupy a single position in the window stack 1728 although itis displayed on both displays 110, 114.

Yet another arrangement of a window stack 1760 is shown in FIGS. 9Cthrough 9E. The window stack 1760 is shown in three “elevation” views.In FIG. 9C, the top of the window stack 1760 is shown. Two sides of thewindow stack 1760 are shown in FIGS. 9D and 9E. In this embodiment, thewindow stack 1760 resembles a stack of bricks. The windows are stackedon each other. Looking from the top of the window stack 1760 in FIG. 9C,only the top most windows in the window stack 1760 are seen in differentportions of the composite display 1764. The composite display 1764represents a logical model for the entire display area of the device100, which can include touch sensitive display 110 and touch sensitivedisplay 114. A desktop 1786 or a window can occupy part or all of thecomposite display 1764.

In the embodiment shown, the desktop 1786 is the lowest display or“brick” in the window stack 1760. Thereupon, window 1 1782, window 21782, window 3 1768, and window 4 1770 are layered. Window 1 1782,window 3 1768, window 2 1782, and window 4 1770 only occupy a portion ofthe composite display 1764. Thus, another part of the stack 1760includes window 8 1774 and windows 5 through 7 shown in section 1790.Only the top window in any portion of the composite display 1764 isactually rendered and displayed. Thus, as shown in the top view in FIG.9C, window 4 1770, window 8 1774, and window 3 1768 are displayed asbeing at the top of the display in different portions of the windowstack 1760. A window can be dimensioned to occupy only a portion of thecomposite display 1760 to “reveal” windows lower in the window stack1760. For example, window 3 1768 is lower in the stack than both window4 1770 and window 8 1774 but is still displayed. A logical datastructure to manage the window stack can be as described in conjunctionwith FIG. 10.

When a new window is opened, the newly activated window is generallypositioned at the top of the stack. However, where and how the window ispositioned within the stack can be a function of the orientation of thedevice 100, the context of what programs, functions, software, etc. arebeing executed on the device 100, how the stack is positioned when thenew window is opened, etc. To insert the window in the stack, theposition in the stack for the window is determined and the touchsensitive display 110, 114 to which the window is associated may also bedetermined. With this information, a logical data structure for thewindow can be created and stored. When user interface or other events ortasks change the arrangement of windows, the window stack(s) can bechanged to reflect the change in arrangement. It should be noted thatthese same concepts described above can be used to manage the one ormore desktops for the device 100.

A logical data structure 1800 for managing the arrangement of windows ordesktops in a window stack is shown in FIG. 10. The logical datastructure 1800 can be any data structure used to store data whether anobject, record, file, etc. The logical data structure 1800 can be storedin any type of database or data storage system, regardless of protocolor standard. In embodiments, the logical data structure 1800 includesone or more portions, fields, attributes, etc. that store data in alogical arrangement that allows for easy storage and retrieval of theinformation. Hereinafter, these one or more portions, fields,attributes, etc. shall be described simply as fields. The fields canstore data for a window identifier 1804, dimensions 1808, a stackposition identifier 1812, a display identifier 1816, and/or an activeindicator 1820. Each window in a window stack can have an associatedlogical data structure 1800. While only a single logical data structure1800 is shown in FIG. 10, there may be more or fewer logical datastructures 1800 used with a window stack (based on the number of windowsor desktops in the stack), as represented by ellipses 1824. Further,there may be more or fewer fields than those shown in FIG. 10, asrepresented by ellipses 1828.

A window identifier 1804 can include any identifier (ID) that uniquelyidentifies the associated window in relation to other windows in thewindow stack. The window identifier 1804 can be a globally uniqueidentifier (GUID), a numeric ID, an alphanumeric ID, or other type ofidentifier. In embodiments, the window identifier 1804 can be one, two,or any number of digits based on the number of windows that can beopened. In alternative embodiments, the size of the window identifier1804 may change based on the number of windows opened. While the windowis open, the window identifier 1804 may be static and remain unchanged.

Dimensions 1808 can include dimensions for a window in the compositedisplay 1760. For example, the dimensions 1808 can include coordinatesfor two or more corners of the window or may include one coordinate anddimensions for the width and height of the window. These dimensions 1808can delineate what portion of the composite display 1760 the window mayoccupy, which may the entire composite display 1760 or only part ofcomposite display 1760. For example, window 4 1770 may have dimensions1880 that indicate that the window 1770 will occupy only part of thedisplay area for composite display 1760, as shown in FIGS. 9C through9E. As windows are moved or inserted in the window stack, the dimensions1808 may change.

A stack position identifier 1812 can be any identifier that can identifythe position in the stack for the window or may be inferred from thewindow's control record within a data structure, such as a list or astack. The stack position identifier 1812 can be a GUID, a numeric ID,an alphanumeric ID, or other type of identifier. Each window or desktopcan include a stack position identifier 1812. For example, as shown inFIG. 9A, window 1 1704 in stack 1 1760 can have a stack positionidentifier 1812 of 1 identifying that window 1704 is the first window inthe stack 1760 and the active window. Similarly, window 6 1724 can havea stack position identifier 1812 of 3 representing that window 1724 isthe third window in the stack 1760. Window 2 1708 can also have a stackposition identifier 1812 of 1 representing that window 1708 is the firstwindow in the second stack 1764. As shown in FIG. 9B, window 1 1744 canhave a stack position identifier 1812 of 1, window 3, rendered inportions 1732 and 1736, can have a stack position identifier 1812 of 3,and window 6 1756 can have a stack position identifier 1812 of 6. Thus,depending on the type of stack, the stack position identifier 1812 canrepresent a window's location in the stack.

A display identifier 1816 can identify that the window or desktop isassociated with a particular display, such as the first display 110 orthe second display 114, or the composite display 1760 composed of bothdisplays. While this display identifier 1816 may not be needed for amulti-stack system, as shown in FIG. 9A, the display identifier 1816 canindicate whether a window in the serial stack of FIG. 9B is displayed ona particular display. Thus, window 3 may have two portions 1732 and 1736in FIG. 9B. The first portion 1732 may have a display identifier 1816for the first display while the second portion 1736 may have a displayidentifier 1816 for the second display 114. However, in alternativeembodiments, the window may have two display identifier 1816 thatrepresent that the window is displayed on both of the displays 110, 114,or a display identifier 1816 identifying the composite display. Inanother alternate embodiment, the window may have a single displayidentifier 1816 to represent that the window is displayed on both of thedisplays 110, 114.

Similar to the display identifier 1816, an active indicator 1820 may notbe needed with the dual stack system of FIG. 9A, as the window in stackposition 1 is active and displayed. In the system of FIG. 9B, the activeindicator 1820 can indicate which window(s) in the stack is beingdisplayed. Thus, window 3 may have two portions 1732 and 1736 in FIG. 9.The first portion 1732 may have an active indicator 1820 while thesecond portion 1736 may also have an active indicator 1820. However, inalternative embodiments, window 3 may have a single active indicator1820. The active indicator 1820 can be a simple flag or bit thatrepresents that the window is active or displayed.

An embodiment of a method 900 for creating a window stack is shown inFIG. 11. While a general order for the steps of the method 1900 is shownin FIG. 11. Generally, the method 1900 starts with a start operation1904 and ends with an end operation 1928. The method 1900 can includemore or fewer steps or can arrange the order of the steps differentlythan those shown in FIG. 11. The method 1900 can be executed as a set ofcomputer-executable instructions executed by a computer system andencoded or stored on a computer readable medium. Hereinafter, the method1900 shall be explained with reference to the systems, components,modules, software, data structures, user interfaces, etc. described inconjunction with FIGS. 1-10.

A multi-screen device 100 can receive activation of a window, in step1908. In embodiments, the multi-screen device 100 can receive activationof a window by receiving an input from the touch sensitive display 110or 114, the configurable area 112 or 116, a gesture capture region 120or 124, or some other hardware sensor operable to receive user interfaceinputs. The processor may execute the Task Management Module 540 mayreceive the input. The Task Management Module 540 can interpret theinput as requesting an application task to be executed that will open awindow in the window stack.

In embodiments, the Task Management Module 540 places the user interfaceinteraction in the task stack 552 to be acted upon by the DisplayConfiguration Module 568 of the Multi-Display Management Module 524.Further, the Task Management Module 540 waits for information from theMulti-Display Management Module 524 to send instructions to the WindowManagement Module 532 to create the window in the window stack.

The Multi-Display Management Module 524, upon receiving instruction fromthe Task Management Module 540, determines to which touch portion of thecomposite display 1760, the newly activated window should be associated,in step 1912. For example, window 4 1770 is associated with the aportion of the composite display 1764 In embodiments, the device statemodule 574 of the Multi-Display Management Module 524 may determine howthe device is oriented or in what state the device is in, e.g., open,closed, portrait, etc. Further, the preferences module 572 and/orrequirements module 580 may determine how the window is to be displayed.The gesture module 576 may determine the user's intentions about how thewindow is to be opened based on the type of gesture and the location ofwhere the gesture is made.

The Display Configuration Module 568 may use the input from thesemodules and evaluate the current window stack 1760 to determine the bestplace and the best dimensions, based on a visibility algorithm, to openthe window. Thus, the Display Configuration Module 568 determines thebest place to put the window at the top of the window stack 1760, instep 1916. The visibility algorithm, in embodiments, determines for allportions of the composite display, which windows are at the top of thestack. For example, the visibility algorithm determines that window 31768, window 4 1770, and window 8 1774 are at the top of the stack 1760as viewed in FIGS. 9C through 9E. Upon determining where to open thewindow, the Display Configuration Module 568 can assign a displayidentifier 816 and possibly dimensions 808 to the window. The displayidentifier 816 and dimensions 808 can then be sent back to the TaskManagement Module 540. The Task Management Module 540 may then assignthe window a stack position identifier 812 indicating the windowsposition at the top of the window stack.

In embodiments, the Task Management Module 540 sends the window stackinformation and instructions to render the window to the WindowManagement Module 532. The Window Management Module 532 and the TaskManagement Module 540 can create the logical data structure 800, in step1924. Both the Task Management Module 540 and the Window ManagementModule 532 may create and manage copies of the window stack. Thesecopies of the window stack can be synchronized or kept similar throughcommunications between the Window Management Module 532 and the TaskManagement Module 540. Thus, the Window Management Module 532 and theTask Management Module 540, based on the information determined by theMulti-Display Management Module 524, can assign dimensions 808, a stackposition identifier 812 (e.g., window 1 1782, window 4 1770, etc.), adisplay identifier 816 (e.g., touch sensitive display 1 110, touchsensitive display 2 114, composite display identifier, etc,), and anactive indicator 820, which is generally always set when the window isat the “top” of the stack. The logical data structure 800 may then bestored by both the Window Management Module 532 and the Task ManagementModule 540. Further, the Window Management Module 532 and the TaskManagement Module 540 may thereinafter manage the window stack and thelogical data structure(s) 800.

FIG. 12 depicts a further window stacking configuration. A plurality ofwindows 1, 2, 3, 4, 5, 6, 7, and 8, whether from the same or differentmulti-screen or single-screen applications, are depicted. The touchsensitive display 110 currently has window 4 in the active displayposition while touch sensitive display 114 currently has window 5 in theactive display position. The stack for touch sensitive display 110, fromtop to bottom, has window 4 in the active display position and windows3, 2, and 1 positioned behind it. The stack for touch sensitive display114, from top to bottom, has window 5 in the active display position andwindows 6, 7, and 8 positioned behind it.

The desktops D1, D2, D3, D4, D5, and D6 are positioned behind the windowstacks. The desktops can be viewed as a desktop stack different from thewindow stack. Viewed in this manner, the touch sensitive display 110 hasa corresponding desktop stack comprising desktops D3, D2, and D1, withdesktop D1 being at the bottom 2300 stack position and with desktop D3at the top stack position being capable of being displayed with window 4(depending on the window position and size (whether maximized orminimized)), and the touch sensitive display 114 has a correspondingdesktop stack has a corresponding desktop stack comprising desktops D4,D5, and D6, with desktop D6 being at the bottom 2304 stack position andwith desktop D4 at the top stack position being capable of beingdisplayed with window 5 (depending on the window position and size(whether maximized or minimized)). Conceptually, the desktops can beviewed as a canvas divided, in this example, into six sections of whichtwo can be displayed, at any one time, the touch sensitive displays 110,114. When the device 100 is in the closed state, this conceptual model,in one configuration, persists. In this configuration, only one windowand desktop stacks can be seen (that corresponding to the primaryscreen) but the other window and desktop stacks are virtual; that is,they are maintained in memory but cannot be seen because the secondaryscreen is not enabled.

Single-screen applications are typically related only to one windowwhile multi-screen applications can be related to one or more windows.The latter hierarchical relationship is depicted in FIG. 8. As shown inFIG. 8, first window 1.1 is a root window, second window 1.1.1 is a nodewindow, and third window 1.1.1.1 is a leaf window. The windows are in ahierarchical tree-like sequence and are controlled by a commonmulti-screen application. The root window 1.1 may be a top level view ofthe hierarchical application window sequence such that there is noparent window corresponding to the root window. The root window may be aparent to a node window. One or more node windows may be provided thatare related as parent/children. A node window may also serve as a leafwindow. By leaf window, it is meant that the leaf window has nocorresponding node screen for which the leaf window is a parent. Assuch, the leaf window does not have any children node windows, Windows1.1.1.1 and 1.1.2 are examples of leaf windows. The root view refers toall of the windows controlled by a multi-screen application at a pointin time.

A number of examples will now be discussed with reference to minimizingand maximizing root view windows and subcomponents thereof. Prior todiscussing the examples, some fundamental rules regarding maximizing andminimizing displayed images will be discussed. A maximize or minimizeoperation is typically initiated by a user gesture, particularly a flipor drag. In a drag gesture, a 1:1 map reaction between the user's digitand the displayed image is used as the user “drags” the displayed imageto the other touch sensitive display. The user typically releases thedisplayed image before it is fully moved to the other touch sensitivedisplay. The initial speed after release is generally decreasedprogressively or gradually until the displayed image is fully located inthe desired position. Too little displacement of the displayed imagegenerally will not cause the image to be relocated. Such a low level ofdisplacement is assumed to be accidental or incidental to the user usingthe device.

In a root view, or set of hierarchically related windows, the user, whenthe device is in dual screen mode, can maximize the related windows ofthe multi-screen application to enable side-by-side viewing of therelated windows (e.g., the parent and child windows), thereby viewingthe window hierarchy as a linear progression, with the top-most windowbeing displayed on the left and the lowest-most or deepest level windowbeing displayed on the right (or vice versa). As discussed below, thisvisual configuration can be controlled using directional transitionsconveying a navigation direction and location of a window in relation toa launching point of the window.

A multi-screen application window generally opens in minimized mode. Acontinuing drag and release gesture when a window of a multi-screenapplication, originally minimized in a first touch sensitive display, isat least half-way across the second touch sensitive display willgenerally cause the window to be maximized, or displayed in both thefirst and second touch sensitive displays. Dragging a window of amulti-screen application originally minimized in a first touch sensitivedisplay to a second touch sensitive display all the way across to thefar edge of the second touch sensitive display will generally maximizethe window across both the first and second touch sensitive displays.When the user continues to drag in the same direction after the windowof the multi-screen application is expanded fully (or maximized acrossboth the first and second touch sensitive displays and touching both far(non-adjacent) edges of the first and second touch sensitive displays),the window will pull away from the far edge of the first touch sensitivedisplay and, once the far edge of the window is half-way across thefirst touch sensitive display, the application window will generallyreposition in minimized mode in the second touch sensitive display.

The flick gesture will not generally maximize a window of a multi-screenapplication but generally will reposition a minimized window of asingle- or multi-screen application. The flick gesture will generallynot minimize window(s) of a maximized application. The flick gesture isa way to move rapidly through the windows of a stack, whether thewindows are of a single- or multi-screen application.

For instance, a user selects an application shortcut on a first desktopD1 to launch a multi-screen application, such as Outlook™. Theapplication opens to display a defined parent or root window 1.1 in thescreen of the first desktop D1 (or the screen from which the applicationwas launched). The user expands or maximizes the application to both thefirst and second touch sensitive displays to display the parent window1.1 and the node window 1.1.1. Once expanded, the node window 1.1.1appears based on rules set by the particular application, e.g., the nodewindow 1.1.1 selected is at a selected position and/or relationship tothe parent window 1.1. The user selects, such as by a tap gesture, thenode window 1.1.1 towards the other first touch sensitive display(displaying the parent window 1.1), causing the parent window 1.1 toslide off-display and the leaf window 1.1.1.1 to appear in the secondtouch sensitive display. If, on the other hand, the user selects, suchas by a tap gesture, the parent window 1.1, the parent window 1.1 movesto and is displayed by the second touch sensitive display, and the nodewindow 1.1.1 slides to the right off the second touch sensitive displayto an inactive display position, and a window 1 (not shown) at ahierarchy level higher than the parent window 1.1 moves into and isdisplayed by the first touch sensitive display

A first example will be applied to FIGS. 13A-C. The first and secondtouch sensitive displays 110, 114 display, respectively, a leaf viewwindow 1.1.1.1 and a second desktop D2 (FIG. 13A). Stated another way,the first touch sensitive display 110 has the leaf view window 1.1.1.1(1308) in an active display position, and the second touch sensitivedisplay 114 has the second desktop D2 in an active display position. Ina gesture capture region 120 or 124 (or in other configurations thefirst or second touch sensitive display 110 or 114) receives, from theuser, a gesture 1300. Exemplary gestures include a drag or flick to theright (though one or more other gestures may be employed). By thegesture 1300, the user seeks to maximize the root view to show the nodewindow 1.1.1 (1304) and the leaf window 1.1.1.1 (1308) in separatedisplays (FIG. 13B). As a general rule, a leaf window (or window havingno child) is positioned on the second touch sensitive display 114. Thus,the leaf window 1.1.1.1 (1308) moves to the active display position onthe second touch sensitive display 114, and the node window 1.1.1 (1304)is moved to the active display position on the first touch sensitivedisplay 110 as shown by FIG. 13C. The second desktop D2, meanwhile,moves to an inactive display position on the second touch sensitivedisplay 114. The leaf window 1.1.1.1 (1308) does this by sliding over tothe second touch sensitive display 114, thereby revealing or uncoveringthe node window 1.1.1 (1304). As will be appreciated, a reverse generalrule could also be applied; that is, the leaf window could be positionedon the first touch sensitive display 110.

A second example will be discussed with reference to FIGS. 14A-C inwhich the first touch sensitive display 110 has a first desktop D1 in anactive display position, and the second touch sensitive display 114 hasthe leaf view window 1.1.1.1 (1308) in an active display position. In agesture capture region 120 or 124 (or in other configurations the firstor second touch sensitive display 110 or 114) receives, from the user, agesture 1300, such as a flick or drag, to the left. By the gesture 1300,the user seeks to maximize the root view to show the node window 1.1.1(1304) and the leaf window 1.1.1.1 (1308) in separate displays (FIG.14B). As a general rule, a leaf window (or window having no child) ispositioned on the second touch sensitive display 114. Thus, the leafwindow 1.1.1.1 (1308) remains in the active display position on thesecond touch sensitive display 114, and the node window 1.1.1 (1304) ismoved to the active display position on the first touch sensitivedisplay 110 as shown by FIG. 14C. The first desktop D1, meanwhile, movesto an inactive display position on the first touch sensitive display110. The node window 1.1.1 (1304) does this by sliding from under theleaf window 1.1.1.1 (1308). As will be appreciated, a reverse generalrule could also be applied; that is, the leaf window could be positionedon the first touch sensitive display 110.

A third example will be discussed with reference to FIGS. 24A-C in whichthe first touch sensitive display 110 has the root window 1.1 (1600) inan active display position (and the node and leaf windows 1.1.1 (1304)and 1.1.1.1 (1308) in inactive display positions), and the second touchsensitive display 114 has the second desktop D2 in an active displayposition. In a gesture capture region 120 or 124 (or in otherconfigurations the first or second touch sensitive display 110 or 114)receives, from the user, a gesture 1300, such as a flick or drag, to theright. By the gesture 1300, the user seeks to maximize the root view toshow the root window 1.1 (1600) and node window 1.1.1 (1304) in separatedisplays (FIG. 24B). As a general rule, whenever a child window (e.g., anode or leaf window) is uncovered through maximization, it is uncoveredon the second touch sensitive display 114. Thus, the root window 1.1(1600) remains in the active display position on the first touchsensitive display 110, and the node window 1.1.1 (1304) is moved to theactive display position on the second touch sensitive display 114 asshown by FIG. 24C. The second desktop D2, meanwhile, moves to aninactive display position on the second touch sensitive display 114. Thenode window 1.1.1 (1304) does this by sliding out from under the rootwindow 1.1 (1600). As will be appreciated, a reverse general rule couldalso be applied; that is, the child window could be positioned on thefirst touch sensitive display 110.

A fourth example will be discussed with reference to FIGS. 25A-C inwhich the first touch sensitive display 110 has the first desktop D1 inan active display position, and the second touch sensitive display 114has the root window 1.1 (1600) in an active display position (and thenode and leaf windows 1.1.1 (1304) and 1.1.1.1 (1308) in inactivedisplay positions). In a gesture capture region 120 or 124 (or in otherconfigurations the first or second touch sensitive display 110 or 114)receives, from the user, a gesture 1300, such as a flick or drag, to theleft. By the gesture 1300, the user seeks to maximize the root view toshow the root window 1.1 (1600) and node window 1.1.1 (1304) in separatedisplays (FIG. 25B). Thus, the node window 1.1.1 (1304) moves to theactive display position on the second touch sensitive display 114, andthe root window 1.1 (1600) is moved to the active display position onthe first touch sensitive display 110 as shown by FIG. 25C. The firstdesktop D1, meanwhile, moves to an inactive display position on thefirst touch sensitive display 110. The root window 1.1 (1600) does thisby sliding over from above the node window 1.1.1 (1304).

A fifth example will be discussed with reference to FIGS. 15A-C in whichthe first touch sensitive display 110 displays the leaf window 1.1.1.1(1308), and the second touch sensitive display 114 displays the seconddesktop D2. In a gesture capture region 120 or 124 (or in otherconfigurations the first or second touch sensitive display 110 or 114)receives, from the user, a gesture 1300, particularly a flick gesture,to the right. By the gesture 1300, the user seeks to move the leafwindow 1.1.1.1 (1308) to the second touch sensitive display 114 toreveal the first desktop D1. As a general rule, a flick gesture willmove the leaf window to the other touch sensitive display. Thus, theleaf window 1.1.1.1 (1308) moves to the active display position on thesecond touch sensitive display 114, and the first desktop D1 moves tothe active display position on the first touch sensitive display 110 asshown by FIG. 15C. The second desktop D2, meanwhile, moves to aninactive display position on the second touch sensitive display 110.

A sixth example will be discussed with reference to FIGS. 26A-C in whichthe first touch sensitive display 110 displays the root window 1.1(1600), and the second touch sensitive display 114 displays the seconddesktop D2. As will be appreciated, the display of a higher level (e.g.,node) window by the device 100 indicates that its related, lower levelwindows are positioned in the same display “underneath” the higher levelwindow (or in inactive display positions in the stack corresponding tothe appropriate display). With reference to FIG. 26A, the display of theroot window 1.1 (1600) indicates that the node window 1.1.1 (1304) andleaf window 1.1.1.1 (1600) are in inactive display positions in thefirst touch sensitive display 110. In a gesture capture region 120 or124 (or in other configurations the first or second touch sensitivedisplay 110 or 114) receives, from the user, a gesture 1300,particularly a flick gesture, to the right. By the gesture 1300, theuser seeks to move the root view to the second touch sensitive display114 to reveal the first desktop D1. As a general rule, a flick gesturewill move the root window (or root view) to the other touch sensitivedisplay (and maintain the relative stack display positions of the rootview). Thus, the root window 1.1 (1600) moves to the active displayposition on the second touch sensitive display 114, and the firstdesktop D1 moves to the active display position on the first touchsensitive display 110 as shown by FIG. 26C. The second desktop D2,meanwhile, moves to an inactive display position on the second touchsensitive display 110.

A seventh example will be applied to FIGS. 16A-C. The first and secondtouch sensitive displays 110, 114 display, respectively, a root window1.1 (1600) and a node window 1.1.1 (1304) (FIG. 16A). Stated anotherway, the first touch sensitive display 110 has the root window 1.1(1600) in an active display position, and the second touch sensitivedisplay 114 has the node window 1.1.1 (1304) in an active displayposition. In a gesture capture region 120 or 124 (or in otherconfigurations the first or second touch sensitive display 110 or 114)receives, from the user, a gesture 1300. Exemplary gestures include adrag or flick to the right. By the gesture 1300, the user seeks tominimize the node window in the second touch sensitive display 114 (FIG.16B). As a general rule, a minimizing a higher level (e.g., root) andlower level (e.g., node) windows from a touch sensitive display is doneso as to maintain the higher level (e.g., root or parent) window 1.1(1600) in the active display position on the minimized view. Thus, theroot window 1.1 (1600) moves to the active display position on thesecond touch sensitive display 114, and the node window 1.1.1 (1304) ismoved to the inactive display position on the second touch sensitivedisplay 114 as shown by FIG. 16C. The first desktop D1, meanwhile, movesto the active display position on the first touch sensitive display 110.The root window 1.1 (1600) does this by sliding over to the second touchsensitive display 114, thereby revealing or uncovering the first desktopD1. As will be appreciated, a reverse general rule could also beapplied; that is, the node window could be maintained in view over theroot window.

An eighth example will be discussed with reference to FIGS. 17A-C inwhich the first touch sensitive display 110 has the root window 1.1(1600) in an active display position, and the second touch sensitivedisplay 114 has the node window 1.1.1 (1304) in an active displayposition. In a gesture capture region 120 or 124 (or in otherconfigurations the first or second touch sensitive display 110 or 114)receives, from the user, a gesture 1300, such as a flick or drag, to theleft. By the gesture 1300, the user seeks to minimize the root view inthe first touch sensitive display 110 (FIG. 17B). The root window 1.1(1600) remains in the active display position on the first touchsensitive display 110, and the node window 1.1.1 (1304) is moved to aninactive display position on the first touch sensitive display 110 asshown by FIG. 17C. The second desktop D2, meanwhile, moves to an activedisplay position on the second touch sensitive display 114. The nodewindow 1.1.1 (1304) does this by sliding under the root window 1.1(1600).

A ninth example will be discussed with reference to FIGS. 18A-C in whichthe first touch sensitive display 110 displays the node window 1.1.1(1304), and the second touch sensitive display 114 displays the leafwindow 1.1.1.1 (1308). In a gesture capture region 120 or 124 (or inother configurations the first or second touch sensitive display 110 or114) receives, from the user, a gesture 1300, particularly a flick ordrag gesture, to the right. By the gesture 1300, the user seeks to movethe node window 1.1.1 (1304) to the second touch sensitive display 114to reveal the first desktop D1 in the first touch sensitive display 110.Thus, the leaf window 1.1.1.1 (1308) moves to an inactive displayposition on the second touch sensitive display 114, and the firstdesktop D1 moves to the active display position on the first touchsensitive display 110 as shown by FIG. 18C. The node window 1.1.1(1304), meanwhile, moves (or slides over the leaf window 1.1.1.1 (1308)to the active display position on the second touch sensitive display114.

A tenth example will be discussed with reference to FIGS. 19A-C in whichthe first touch sensitive display 110 displays the node window 1.1.1(1304), and the second touch sensitive display 114 displays the leafwindow 1.1.1.1 (1308). In a gesture capture region 120 or 124 (or inother configurations the first or second touch sensitive display 110 or114) receives, from the user, a gesture 1300, particularly a flick ordrag gesture, to the left. By the gesture 1300, the user seeks to movethe leaf window 1.1.1.1 (1308) to the first touch sensitive display 110to reveal the second desktop D2 in the second touch sensitive display114. Thus, the leaf window 1.1.1.1 (1308) moves (or slides under thenode window 1.1.1 (1304)) to an inactive display position on the firsttouch sensitive display 110, and the second desktop D2 moves to theactive display position on the second touch sensitive display 114 asshown by FIG. 19C. The node window 1.1.1 (1304), meanwhile, remains inthe active display position on the first touch sensitive display 110.

In a further example shown in FIGS. 20A-C, the device 100 is in duallandscape display mode. Unlike dual portrait display mode, the device,in the dual landscape display mode, can present one view, and not two.This capability, in turn, affects the maximization and minimizationrules.

The first touch sensitive display 110 displays a minimized root window1.1 (1600), and the second touch sensitive display 114 displays a seconddesktop D2. The root window 1.1 (1600) is minimized in that it occupiesonly one of the primary and secondary screens 104 and 108. In a gesturecapture region 120 or 124 (or in other configurations the touchsensitive display 110 or 114) receives, from the user, a gesture 1300,such as a flick or drag gesture downwards. By the gesture 1300, the userseeks to maximize the root window 1.1 (1600) by displaying the rootwindow on both the first and second touch sensitive displays 110 and114. As shown by FIG. 20B, the root view 1.1 slides downwards to coverthe second touch sensitive display 114. Thus, the root window 1.1 (1600)is in the active display position in both the first and second touchsensitive displays 110 and 114 (FIG. 20C).

A further example is shown in FIGS. 21A-C. With reference to FIG. 21A,the first touch sensitive display 110 displays a first desktop D1, andthe second touch sensitive display 114 displays a minimized root window1.1 (1600). In a gesture capture region 120 or 124 (or in otherconfigurations the touch sensitive display 110 or 114) receives, fromthe user, a gesture 1300, such as a flick or drag gesture upwards. Bythe gesture 1300, the user seeks to maximize the root window 1.1 (1600)by displaying the root window on both the first and second touchsensitive displays 110 and 114. As shown by FIG. 21B, the root view 1.1slides upwards to cover the second touch sensitive display 114. Thus,the root window 1.1 (1600) is in the active display position in both thefirst and second touch sensitive displays 110 and 114 (FIG. 21C).

With reference to FIGS. 22A-C, a further example will be discussed. Withreference to FIG. 22A, the first touch sensitive display 110 displaysthe first desktop D1, and the second touch sensitive display 114displays the root window 1.1 (1600). As will be appreciated, the displayof a higher level (e.g., node) window by the device 100 indicates thatits related, lower level windows are positioned in the same display“underneath” the higher level window (or in inactive display positionsin the stack corresponding to the appropriate display). With referenceto FIG. 22A, the display of the root window 1.1 (1600) indicates thatthe node window 1.1.1 (1304) and leaf window 1.1.1.1 (1600) are ininactive display positions in the second touch sensitive display 110. Ina gesture capture region 120 or 124 (or in other configurations thefirst or second touch sensitive display 110 or 114) receives, from theuser, a gesture 1300, particularly a flick gesture, upwards. By thegesture 1300, the user seeks to move the root view to the first touchsensitive display 110 to reveal the second desktop D2. As a generalrule, a flick gesture will move the root window (or root view) to theother touch sensitive display (and maintain the relative stack displaypositions of the root view). Thus, the root window 1.1 (1600) moves tothe active display position on the first touch sensitive display 110,and the second desktop D2 moves to the active display position on thesecond touch sensitive display 114 as shown by FIG. 22C. The firstdesktop D1, meanwhile, moves to an inactive display position on thefirst touch sensitive display 110.

A further example is shown in FIGS. 23A-C. With reference to FIG. 23A,the first and second touch sensitive displays 110 and 114 display amaximized root window 1.1 (1600). In a gesture capture region 120 or 124(or in other configurations the touch sensitive display 110 or 114)receives, from the user, a gesture 1300, such as a flick or drag gestureupwards. By the gesture 1300, the user seeks to minimize the root window1.1 (1600) by displaying the root window in the first touch sensitivedisplay 110 to reveal the second desktop D2 in the second touchsensitive display 114. As shown by FIG. 23B, the root view 1.1 in thesecond touch sensitive display 114 slides upwards, revealing the seconddesktop D2. Thus, the root window 1.1 (1600) is in the active displayposition in the first touch sensitive display 110 while the seconddesktop is in the active display position in the second touch sensitivedisplay 114 (FIG. 23C).

In the various examples, middleware 520, particularly one or more of theMulti-Display Management (MDM) class 524, a Surface Cache class 528, aWindow Management class 532, an Activity Management class 536, and anTask Management class 540, independently or collectively, receive acommand to manipulate a displayed set of related windows from amulti-screen application in a predetermined manner, such as by detectinga gesture 1300 (step 2700). In response, middleware 520 determineswhether the set of related windows is currently maximized (in which caseeach of the touch sensitive displays 110 and 114 display one of therelated windows) or minimized (in which case only one of the touchsensitive displays 110 or 114 displays one of the windows) (step 2704).In decision diamond 2708, the middleware 520 decides how to process thecommand based on whether the window(s) is maximized or minimized. Whenmaximized, the middleware 520 determines whether the device 100 is inthe portrait or landscape display mode and, when in the landscapedisplay mode, which of the touch sensitive displays 110 and 114 is ontop and which is on the bottom (step 2712). When in portrait displaymode, the middleware 520 causes the lower level window (e.g., leafwindow 1.1.1.1) to be displayed on a predetermined one of the left orright touch sensitive display. When in landscape display mode, themiddleware 520 causes the lower level window to be displayed on apredetermined one of the upper or lower touch sensitive display. Whenthe related window is minimized, the middleware 520 determines whetherthe device 100 is in the portrait or landscape display mode and, when inthe landscape display mode, which of the touch sensitive displays 110and 114 is on top and which is on the bottom (step 2716). When inportrait display mode, the middleware 520 causes the lower level windowto no longer be displayed on a predetermined one of the left or righttouch sensitive display. When in landscape display mode, the middleware520 causes the lower level window to no longer be displayed on apredetermined one of the upper or lower touch sensitive display.

The exemplary systems and methods of this disclosure have been describedin relation to communication devices. However, to avoid unnecessarilyobscuring the present disclosure, the preceding description omits anumber of known structures and devices. This omission is not to beconstrued as a limitation of the scopes of the claims. Specific detailsare set forth to provide an understanding of the present disclosure. Itshould however be appreciated that the present disclosure may bepracticed in a variety of ways beyond the specific detail set forthherein.

Furthermore, while the exemplary aspects, embodiments, and/orconfigurations illustrated herein show the various components of thesystem collocated, certain components of the system can be locatedremotely, at distant portions of a distributed network, such as a LANand/or the Internet, or within a dedicated system. Thus, it should beappreciated, that the components of the system can be combined in to oneor more devices, such as a communication device, or collocated on aparticular node of a distributed network, such as an analog and/ordigital telecommunications network, a packet-switch network, or acircuit-switched network. It will be appreciated from the precedingdescription, and for reasons of computational efficiency, that thecomponents of the system can be arranged at any location within adistributed network of components without affecting the operation of thesystem. For example, the various components can be located in a switchsuch as a PBX and media server, gateway, in one or more communicationsdevices, at one or more users' premises, or some combination thereof.Similarly, one or more functional portions of the system could bedistributed between a telecommunications device(s) and an associatedcomputing device.

Furthermore, it should be appreciated that the various links connectingthe elements can be wired or wireless links, or any combination thereof,or any other known or later developed element(s) that is capable ofsupplying and/or communicating data to and from the connected elements.These wired or wireless links can also be secure links and may becapable of communicating encrypted information. Transmission media usedas links, for example, can be any suitable carrier for electricalsignals, including coaxial cables, copper wire and fiber optics, and maytake the form of acoustic or light waves, such as those generated duringradio-wave and infra-red data communications.

Also, while the flowcharts have been discussed and illustrated inrelation to a particular sequence of events, it should be appreciatedthat changes, additions, and omissions to this sequence can occurwithout materially affecting the operation of the disclosed embodiments,configuration, and aspects.

A number of variations and modifications of the disclosure can be used.It would be possible to provide for some features of the disclosurewithout providing others.

In other embodiments, other rules may be applied. For example, thepreferred orientations of the higher and lower level related windows isdifferent from the orientations described above.

In yet another embodiment, the systems and methods of this disclosurecan be implemented in conjunction with a special purpose computer, aprogrammed microprocessor or microcontroller and peripheral integratedcircuit element(s), an ASIC or other integrated circuit, a digitalsignal processor, a hard-wired electronic or logic circuit such asdiscrete element circuit, a programmable logic device or gate array suchas PLD, PLA, FPGA, PAL, special purpose computer, any comparable means,or the like. In general, any device(s) or means capable of implementingthe methodology illustrated herein can be used to implement the variousaspects of this disclosure. Exemplary hardware that can be used for thedisclosed embodiments, configurations and aspects includes computers,handheld devices, telephones (e.g., cellular, Internet enabled, digital,analog, hybrids, and others), and other hardware known in the art. Someof these devices include processors (e.g., a single or multiplemicroprocessors), memory, nonvolatile storage, input devices, and outputdevices. Furthermore, alternative software implementations including,but not limited to, distributed processing or component/objectdistributed processing, parallel processing, or virtual machineprocessing can also be constructed to implement the methods describedherein.

In yet another embodiment, the disclosed methods may be readilyimplemented in conjunction with software using object or object-orientedsoftware development environments that provide portable source code thatcan be used on a variety of computer or workstation platforms.Alternatively, the disclosed system may be implemented partially orfully in hardware using standard logic circuits or VLSI design. Whethersoftware or hardware is used to implement the systems in accordance withthis disclosure is dependent on the speed and/or efficiency requirementsof the system, the particular function, and the particular software orhardware systems or microprocessor or microcomputer systems beingutilized.

In yet another embodiment, the disclosed methods may be partiallyimplemented in software that can be stored on a storage medium, executedon programmed general-purpose computer with the cooperation of acontroller and memory, a special purpose computer, a microprocessor, orthe like. In these instances, the systems and methods of this disclosurecan be implemented as program embedded on personal computer such as anapplet, JAVA® or CGI script, as a resource residing on a server orcomputer workstation, as a routine embedded in a dedicated measurementsystem, system component, or the like. The system can also beimplemented by physically incorporating the system and/or method into asoftware and/or hardware system.

Although the present disclosure describes components and functionsimplemented in the aspects, embodiments, and/or configurations withreference to particular standards and protocols, the aspects,embodiments, and/or configurations are not limited to such standards andprotocols. Other similar standards and protocols not mentioned hereinare in existence and are considered to be included in the presentdisclosure. Moreover, the standards and protocols mentioned herein andother similar standards and protocols not mentioned herein areperiodically superseded by faster or more effective equivalents havingessentially the same functions. Such replacement standards and protocolshaving the same functions are considered equivalents included in thepresent disclosure.

The present disclosure, in various aspects, embodiments, and/orconfigurations, includes components, methods, processes, systems and/orapparatus substantially as depicted and described herein, includingvarious aspects, embodiments, configurations embodiments,subcombinations, and/or subsets thereof. Those of skill in the art willunderstand how to make and use the disclosed aspects, embodiments,and/or configurations after understanding the present disclosure. Thepresent disclosure, in various aspects, embodiments, and/orconfigurations, includes providing devices and processes in the absenceof items not depicted and/or described herein or in various aspects,embodiments, and/or configurations hereof, including in the absence ofsuch items as may have been used in previous devices or processes, e.g.,for improving performance, achieving ease and\or reducing cost ofimplementation.

The foregoing discussion has been presented for purposes of illustrationand description. The foregoing is not intended to limit the disclosureto the form or forms disclosed herein. In the foregoing DetailedDescription for example, various features of the disclosure are groupedtogether in one or more aspects, embodiments, and/or configurations forthe purpose of streamlining the disclosure. The features of the aspects,embodiments, and/or configurations of the disclosure may be combined inalternate aspects, embodiments, and/or configurations other than thosediscussed above. This method of disclosure is not to be interpreted asreflecting an intention that the claims require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive aspects lie in less than all features of a singleforegoing disclosed aspect, embodiment, and/or configuration. Thus, thefollowing claims are hereby incorporated into this Detailed Description,with each claim standing on its own as a separate preferred embodimentof the disclosure.

Moreover, though the description has included description of one or moreaspects, embodiments, and/or configurations and certain variations andmodifications, other variations, combinations, and modifications arewithin the scope of the disclosure, e.g., as may be within the skill andknowledge of those in the art, after understanding the presentdisclosure. It is intended to obtain rights which include alternativeaspects, embodiments, and/or configurations to the extent permitted,including alternate, interchangeable and/or equivalent structures,functions, ranges or steps to those claimed, whether or not suchalternate, interchangeable and/or equivalent structures, functions,ranges or steps are disclosed herein, and without intending to publiclydedicate any patentable subject matter.

1-17. (canceled)
 18. A method, comprising: receiving via a gesturecapture region, by processor executable middleware in a multi-displaycommunication device, a command to at least one of minimize and maximizea set of related windows from a common multi-screen application, the setof related windows comprising a higher level window and a lower levelwindow at least one of displayed and to be displayed by a first touchsensitive display and a second touch sensitive display, wherein a firstgesture is executed on a first gesture capture region with one finger ofthe user placed on the first gesture capture region, and wherein asecond gesture is executed on a second gesture capture region withanother finger of the user placed on the second gesture capture region;applying, by the processor executable middleware, at least one of thefollowing rules: (B1) when the set of related windows is to beminimized, selecting a first touch sensitive display for displaying thehigher level window and ceasing to display the lower level window on thesecond touch sensitive display; and (B2) when the set of related windowsis to be maximized, selecting a first touch sensitive display fordisplaying one of the higher and lower level windows and causing theother of the higher and lower level windows to be displayed on thesecond touch sensitive display.
 19. The method of claim 18, wherein rule(B2) applies.
 20. The method of claim 19, wherein the command is a dragor a flick, wherein neither the higher nor lower level window isdisplayed in the first touch sensitive display when the gesture isreceived, and wherein the lower level window appears to move from thesecond touch sensitive display to the first touch sensitive display,thereby revealing the higher level window in the second touch sensitivedisplay.
 21. The method of claim 19, wherein the command is a drag or aflick, wherein the lower level window is in the first touch sensitivedisplay when the gesture is received, wherein the higher level windowappears to move from the first touch sensitive display to the secondtouch sensitive display, whereby the lower level window is displayed bythe first touch sensitive display and the higher level window isdisplayed by the second touch sensitive display.
 22. The method of claim19, wherein the multi-display communication device is in the portraitdisplay mode and wherein the first touch sensitive display is theright-most touch sensitive display.
 23. The method of claim 18, whereinrule (B1) applies.
 24. The method of claim 23, wherein the command is adrag or a flick, wherein the higher and lower level window areconcurrently displayed in the first touch sensitive display and secondtouch sensitive display when the gesture is received, wherein the lowerlevel window is displayed in the first touch sensitive display when thegesture is received, and wherein the higher level window appears to movefrom the second touch sensitive display to the first touch sensitivedisplay, thereby covering the lower level window in the second touchsensitive display.
 25. The method of claim 23, wherein the command is adrag or a flick, wherein the higher and lower level window areconcurrently displayed in the first touch sensitive display and thesecond touch sensitive display when the gesture is received, wherein thehigher level window is displayed in the first touch sensitive displaywhen the gesture is received, and wherein the lower level window appearsto move from the second touch sensitive display to the first touchsensitive display, thereby disappearing under the higher level window inthe second touch sensitive display.
 26. A non-transient and tangiblecomputer readable medium comprising processor executable instructions toperform the steps of claim
 18. 27. A communication device, comprising:at least first and second touch sensitive displays to display windows; aprocessor; and a computer readable memory, the computer readable memorycomprising processor executable middleware operable to: receive via agesture capture region a command to at least one of minimize andmaximize a set of related windows from a common multi-screenapplication, the set of related windows comprising a higher level windowand a lower level window at least one of displayed and to be displayedby at least first and second touch sensitive displays to displaywindows, wherein a first gesture is executed on a first gesture captureregion with one finger of the user placed on the first gesture captureregion, and wherein a second gesture is executed on a second gesturecapture region with another finger of the user placed on the secondgesture capture region; apply at least one of the following rules: (i)when the set of related windows is to be minimized, selecting a firsttouch sensitive display for displaying the higher level window andceasing to display the lower level window on the second touch sensitivedisplay; and (ii) when the set of related windows is to be maximized,selecting a first touch sensitive display for displaying one of thehigher and lower level windows and causing the second of the higher andlower level window to be displayed on the second touch sensitivedisplay.
 28. The device of claim 27, wherein rule (ii) applies.
 29. Thedevice of claim 28, wherein the command is a drag or a flick, whereinneither the higher nor lower level window is displayed in the firsttouch sensitive display when the gesture is received, and wherein thelower level window appears to move from the second touch sensitivedisplay to the first touch sensitive display, thereby revealing thehigher level window in the second touch sensitive display.
 30. Thedevice of claim 28, wherein the command is a drag or a flick, whereinthe lower level window is in the first touch sensitive display when thegesture is received, wherein the higher level window appears to movefrom the first touch sensitive display to the second touch sensitivedisplay, whereby the lower level window is displayed by the first touchsensitive display and the higher level window is displayed by the secondtouch sensitive display.
 31. The device of claim 28, wherein themulti-display communication device is in the portrait display mode andwherein the first touch sensitive display is the right-most touchsensitive display.
 32. The device of claim 27, wherein rule (i) applies.33. The device of claim 32, wherein the command is a drag or a flick,wherein the higher and lower level window are concurrently displayed inthe first touch sensitive display and second touch sensitive displaywhen the gesture is received, wherein the lower level window isdisplayed in the first touch sensitive display when the gesture isreceived, and wherein the higher level window appears to move from thesecond touch sensitive display to the first touch sensitive display,thereby covering the lower level window in the second touch sensitivedisplay.
 34. The device of claim 32, wherein the command is a drag or aflick, wherein the higher and lower level window are concurrentlydisplayed in the first touch sensitive display and second touchsensitive display when the gesture is received, wherein the higher levelwindow is displayed in the first touch sensitive display when thegesture is received, and wherein the lower level window appears to movefrom the second touch sensitive display to the first touch sensitivedisplay, thereby disappearing under the higher level window in thesecond touch sensitive display.